We can't have coffee machines (unless we smuggle them in, and we do, but the smell gives them away quickly) and are stuck with vending/serving machines. That thing is not even coffee, it's really just a caffeine fix in a horrible and overpriced beverage.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
To be fair the coffee from these machines is usually horrible.
There is a major distinction between machines making coffee from some concentrate, and those grinding beans on the fly. The whole beans variant delivers coffee that is certainly drinkable. Obviously, they cannot in 20 seconds get the same aroma as properly brewed coffee, but it is a lot better than the concentrate. Our current machine even has containers for two different kinds of coffee beans.
The major disadvantage of these machines is that with twenty people in a row to fill their coffee cups, it takes time. They are great for one or two cups, but if you want coffee for a meeting with a lot of participants, you rather go to the canteen to pick up a couple large thermoses of properly brewed coffee.
Spending a small fortune to slowly get from A to B, then B back to A, either in a car (wears out the vehicle quickly, costs a fortune, very slow), on a train (not a lot faster, crowded, smelly, liable to delays and cancellations), on a bicycle (slow, wide open to the elements, liable to death or physical damage, breathing in fumes, will stink all day unless the company provides showers), or even by motorcycle (faster, but wears out the vehicle quickly, wide open to the elements, liable to death or physical damage, breathing in fumes).
Ah! Spending an hour each way every day on a nice big motorbike - unless someone did something really stupid, in which case double that. And they did something stupid at least once a week. The stress levels, the need to drink to reduce those so I could sleep.
My word, but I miss that, and I'd go back to it like a shot!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
Have you tried explaining to a worky that the thing they don't get isn't really an application problem, it is in fact that they have never done the first time set up that the application consultant showed them 3 years ago? Its very much easier to give them a five minute training session and close the ticket having helped rather than argue out the fact that they shouldn't have raised the ticket in the first place, then argue with their boss when it is escalated, his boss when it is escalated again, your own boss when the production director has a word in her ear and so on. The guilty process is of course all nicely documented in a manual, but it should be noted this is a manual IT never got, it was written by third party application consultants and was kept by one of the staff who does the work. Of course he\she knows all about it but no-one ever thinks to ask them. Instead when a new guy starts they always raise a ticket on the IT support system. The ticket wrangler fires that into applications development because it is an application after all. So under normal working in the office conditions we take a nice walk out to the shop-floor, or if we are really lucky an ever nicer stroll to one of the neighbouring buildings. We then have a pleasant 5 minutes talking directly to a fellow human or two, exchanging jokes. A lot of fingers get pointed at screens, we read the words written on them (which is a skill that users never acquire). Then like a magician click the relevant button, check box, or whatever. We show the user what we've done and it all works hooray everyone is happy. If we are really lucky we find the manual and add it to our system (that rarely happens). Now try that on teams!
Last Visit: 31-Dec-99 18:00 Last Update: 10-Aug-22 3:40