Re: Why on earth would AWS want to build 3 datacentres so close together?
Maybe the guy installing all the servers only has one boot floppy and a bicycle...
2378 publicly visible posts • joined 4 Aug 2009
Doesn't surprise me - it completely fails the "fit for purpose" label. I tried it out a couple of years ago and found it wasn't even possible to input all the relevant details about the way I worked. The result it gave for me was, as expected, completely wrong.
Many years ago I wrote some code which automated minor schema changes in MySQL for websites. It's still in use and handles:
* creating tables and their indexes in newly set up databases - all tables are automatically created the first time the website is accessed
* adding new fields added to a table (in most cases it can add new fields to a primary key);
* deleting non-critical (e.g. non-primary key) fields;
* adding or removing indexes;
* renaming fields provided no more than one field of a particular type and length is changed simultaneously. If it discovers, say, two VARCHAR(100) fields being renamed simultaneously it reports that it has no idea which one needs renaming to what new name and gracefully exits;
* non-destructive field type changes - i.e. nothing that should lose data. E.g. changing VARCHAR(40) to VARCHAR(100), TEXT to LONGTEXT, INT to BIGINT.
The code that does this compares the schema derived from the code view of it against the MySQL view of it (from the DESCRIBE statement) and runs the appropriate update depending on the changes detected. The code is either executed once a day or if an SQL statement fails. So, adding a new field to a table (via the code) and having that field requested will silently fail the first time it is used, which causes it to then call the code that updates the schema. Then it tries the SQL statement a second time (a second fail will stop the program). So, the whole process is transparent to the user who just sees a new field added and the system appears to carry on without a hiccup.
The whole thing removes about 99% of the need for manual hacking around with the database so has probably saved me hours of time.
A friend of mine had problems with her computer. So, she reached behind it hoping to find a reset switch. She found a switch without any problem and managed to switch the PSU from the normal 220 volts to 110 volts. I managed to rescue some of the data off the hard drive - the motherboard, CPU and RAM were all fried.
Another tale from my apprentice TV engineering days.
I was sent out with an engineer called Mack to help collect a TV that was no longer required by the family renting it. The TV was on one side of the fireplace, the double mains socket on the other. At some point in the past the mains lead had been extended (using a now-illegal taped up connection) by someone in the family. The extension part of the lead was pinned to the skirting board by cable clips before it ran underneath the carpet and around the fireplace to disappear behind a cabinet before reaching the wall socket. Mack asked if they wanted to keep their extension wire - they did - so he asked them to unplug the other end, which they did. He got out his side cutters and chopped through the wire next to where the taped up joint was. There was a loud bang, Mack was suddenly wearing a very surpised expression and the side cutters, whose handles were thankfully insulated, now had a hole where their blades had previously met.
"Oh," said the member of the family who had done the unplugging, "I think it might have been the other plug."
Now that takes me back! Our first TV was rented from DER when the family lived in London - it was probably around 1960. The first one we had was actually a combined TV + radio receiver. We were forever calling the engineers out because the radio part kept going wrong. I think it got swapped out for a TV-only type after a while (we already had a separate valve radio at the time). I do remember that you had to turn both the TV and radios on at least 5 minutes before the start of any programme you wanted to watch or listen to as they needed that time to "warm up".
Though I never saw it myself, one Rediffusion customer still had a BBC-only TV that was still going strong in the mid-1970s. He'd had it since before ITV went on the air in my area (which, by then, was East Anglia - so 1959). Like your parents, I seem to remember the guy was very reluctant to upgrade.
Because Ceefax was "stored" in the top few scan lines of each TV picture frame, it gave us TV engineers a fine old time running around people's houses in the early 1970s as older TVs started to display the "funny moving dots" at the top of the screen. We had to either adjust the height* but some sets with iffy flyback also required some of the internal vertical alignment settings poking around with as well.
* for those customers incapable** of doing it for themselves.
** there were plenty of those - though they weren't as bad as the ones that took the backs of their rented TVs and played with the controls themselves. We even had one guy who had a habit of swapping valves around and then phoning up to complain that his set had stopped working!
...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)