a UK government IT platform
.....^^^^^^^^^^^^^^^^^ -- well that's the problem, right there!
2659 publicly visible posts • joined 4 Aug 2009
...instead of having it burn up during reentry, they could include a small container of hibernating woodworm* that will be released at the appropriate time and eat the entire thing up.
* and, possibly, metalworm** for the non-wooden parts.
** ah, wait, I think I can see a slight flaw in my idea...
Back when I was an apprentice TV engineer whenever we had a lot of work on we'd call in a retired engineer to help out. The guy was in his late 60s and, having worked in the trade for donkeys years, he seemed to be completely immune to electric shocks. I once saw him check to see if a ceiling light bulb socket was live by deliberately sticking his fingers in it. "Yep," he said, a few seconds later - so we replaced the bulb.
Not IT related but I've got a couple here:
1) Back when I was a teenager my second job was an apprentice TV engineer. Poking around in the high voltage areas of a TV with a screwdriver and not a lot of teenage wisdom would occasionally result in accidentally earthing part of said screwdriver's shaft to the chassis while the tip was in contact with something very much NOT at earth potential. The resulting spark would often temporarily spot weld the screwdriver to the chassis! Good job this was back in the valve days as those things were far more resilient to weird voltages being thrown around than the transistorised replacements that had started coming along around the same time.
2) A few years ago I had a guy out to do the regular yearly service on my gas combi boiler. He'd cleaned everything up and partly re-assembled it and was testing how well the water was heating up before putting the main case back on. At the same time he was looking around for a screwdriver that he'd misplaced. Then he noticed a "slight" irregularity through the small window that gave a view into the burner - he'd found his screwdriver! A hasty disassembly and the screwdriver, whose plastic handle was by now slightly melted, was recovered! The following year he was still proudly using the same screwdriver...
And that's why I am sticking with my secondhand office chair which is probably pushing at least 30 years old by now.
The unadjustable but detachable arms were removed very early on as they were giving me shoulder ache. The seat was recovered back around 2005 after the offspring of a deceased next door neighbour skipped her old furniture in the house clearout - my good old Stanley knife (1960s vintage and previously owned by my father) liberated the as-good-as-new back velvet material from the otherwise well-worn-out sofa which is why the seat is red and the back support is the original brown. The air cylinder packed up a couple of years ago so a bit of unused plastic waste pipe now keeps the seat at the appropriate height.
I've tried other chairs but this one is still the most comfortable - I think I will alter my will to make sure it gets cremated with me when I shuffle off my mortal coil!
Well, it's Microsoft* where security has always been an afterthought (if it's ever "thought" in the first place).
* Actually, you can probably substitute almost any computer software company here. It seems to me that security is something that's always patched in later but is NEVER part of the mix of original ingredients.
Before realising it was a date, my first thought on seeing that number was, "Blimey, he's talking about the first disk drive I ever owned."
I've been running dual monitors on both my PCs for years until a couple of weeks ago when one of my cats managed to jump on top of one monitor and kick it over so that its face hit the mouse. On first inspection there didn't even appear to be a scratch on the monitor's screen surface. Then I turned it on and discovered that, beneath the surface, the LED part of the screen had shattered!
Some people can't!
I was once in an office where another member of staff (let's call him Colin, for that was his name and this isn't a Who Me?) was trying to explain to a customer on the phone how to scroll down a long drop-down menu list in order to view the items that were off the bottom of it. Colin was the utmost in polite helpfulness, which didn't disguise the fact that the person on the other end of the phone line was someone who obviously had problems with computers (and possibly thinking and breathing at the same time). I was in stitches laughing by the time (many minutes later) Colin had finally got the customer to realise what those bars were for on the right of the screen or drop-down menu and how to move them - maybe he'd previously thought they were just random decoration or something. What Colin said AFTER the customer had finally got a clue and was off the phone was far less polite!
Oh yes - I remember it well - I was doing IT Support between 1993 and 1998 - fun times (he says, tongue firmly placed in cheek!).
As Windows at that time was just a graphical shell on top of DOS sometimes a crash meant that you just had to type WIN again at the DOS prompt and not need to do a full reboot.
Windows 95/98 wasn't much better but, because they'd made an attempt to hide DOS, crashes would usually require a reboot. There was also the fun fact that, should Windows 95/98 manage to stay up and running without crashing*, then it would automatically fall over after 49.7 days due to a counter exceeding its limit and resetting to zero**!
* i.e. turned on and not made to do anything AT ALL!
** possibly this was fixed in 98se - there are patches for earlier versions.
More details at http://web.archive.org/web/20111224012719/http://support.microsoft.com/kb/216641
Maybe it should be along the lines of:
Error code for techies: Server error 500
Translation for normal humans*: Hey, it's not my fault! Me (the bit you're holding in your hand) is working fine. I'm trying to talk to another bit a long way away out on teh interwebs. Teh interwebs seem to be working fine as I am managing to shout all the way to other bit. But the other bit isn't talking back in a way that I can understand. Until it does there's not a lot I can do at my end. I suspect coffee is called for at your end. If you're not at home should I try to find the nearest coffee shop (within walking distance**)? While you enjoy your coffee I will keep trying to talk to the other bit and I will ding at you when things are all happy again.
Error messages like this will certainly not add to the app bloat much, well maybe a little (ok, a lot then).
(* yes, I know what that is implying! :)
(** added if the thing the user is trying to get working is a Tesla***)
(*** other electric vehicles as amazing**** as Teslas are available)
(**** stop laughing)
...in most cases the software used will be Excel (probably an old unsupported version) that's running lots of macros that were programmed by someone who no longer works for the institution, and no one there has any clue how it works, so they will leave it to do its "magic" until the day it dies*.
* which will be 2 weeks before it needs to be used for something super-critical whose deadline can't be moved.
Absolutely!
One place I worked at had (for a while) a policy of IT bods shadowing non-IT bods for a short period to see how the non-IT areas worked. Often the benefit was two-way - IT bods understanding how other areas worked and what issues they contended with + being able to suggest improvements (that's PROPER useful improvements as opposed to top-level-management imposed ones) where appropriate.
Later on that policy seemed to slip when changes at the top occurred and I buggered off about a year later after seeing the general downward march into stupidity resulting from said top management changes.
Similar story except, in my case, the client "didn't want to bother" me by asking for a new fields in a customer database table, added secondary data (I think it was eBay and/or Amazon IDs and sometimes both) to the phone number field. 3 years down the line they needed to have this data separated and it took far longer (and therefore cost them more) to unpick the mess, decode which bits were phone number(s) and which were IDs and shove them into separate fields.
"we fixed an issue that kept putting the words 'we fixed an issue' at the beginning of all our bug fix reports."
"we fixed an issue that meant the fix that was supposed to prevent putting the words 'we fixed an issue' at the beginning of all our bug fix reports really worked this time."
"we fixed an issue that meant the fix that was supposed to really work this time to fix the problem of putting the words 'we fixed an issue' at the beginning of all our bug fix reports did actually work this time even though it didn't last time."
"we fixed an issue ... oh fuck it, it's pub o'clock - just install Linux instead!"