Re: As is usual Scott Adams has already been there ....
I'm just wondering what colour t-shirt to put on mine... https://images.app.goo.gl/KEMPbPvUPnLTFL128
113 posts • joined 20 Feb 2012
many moons ago I worked in an office where I used to have to hide my coffee cup every night because the cleaners thought it was a good idea to periodically dump any cups they could lay their hands into a bucket of bleach, presumably to get the tannin stains off the tea-drinkers' cups. Took a good couple of days to get rid of the hint of bleach taste drinking coffee so god knows how bad it must have tasted drinking tea out of them!
A long(ish) time ago, in the late 90s/early 00s I was working for a company where I had spent a fair few years doing coding on a PC based Retail Point of Sale system.
We also provided servicedesk services for a variety of retail chains in the UK and used a fairly low-to-mid-range system, called Heat, to log calls for all the different customers.
I was given the task of seeing if we could make it multi-tenant so that calls could be easily logged and managed for each customer using categories, SLAs, and stuff like that tailored for each customer and to make it easy to switch between different customers within the system when taking calls.
After a bit of time playing with the out of the box customisation options, which were mostly around tweaking fields on forms and setting-up system wide categories,SLAs,escalation routes, I ended-up implementing a whole load of functionality using triggers and stored procedures on the back end database, which was SQL Server 7.0.
I had never even clapped eyes on SQL Server before this - The PoS system I had worked on used a flat file back end database and I had no SQL Server training (of course!) so I pretty much learned on the hoof and had no support from the people who had originally installed the system.
To cut a long story short, I accidentally truncated the core call reference table that everything else hung off pretty much at the busiest time of the day! There were no Pk/Fk relationships within the database to stop that happening - all the relationships were handled within the software itself.
I couldn't just restore the database without kicking everyone out of the system and causing a fair amount of TITSUP* so, after about 30 seconds of wild panic, I ended up restoring to another database everything up to the last transaction log backup, which I had thankfully enabled a couple of weeks previously after discovering the woeful backup strategy that had been left by the original installers, and copied the restored data back over to the live database.
All done in 15 minutes flat! Hardly anyone even noticed there had been a problem and I found a dark corner to go and recover my sanity!
Needless to say, I was much more careful about using the truncate command after that....
On the plus side, I moved to a better paid DBA job in the finance sector a year or so later off the back of that project!
* Total Inability To Support Usual PoSProblems
You can bet your bottom dollar that the DOD Azure deployment won't be running on any of the public cloud kit, will have extra layers of redundancy and will be much more strictly controlled, in terms of patching/updates.
For me, the rot had set in during the Computeraid days - I was in an office outside Glasgow and head office/sales was Farnborough. Sales didn't have a clue about using our product ( till software) as a way in to then sell other nicely profitable services off the back of it. They were only interested in stuff you could throw over the wall and forget about
I worked for Getronics briefly in the early noughties, having started my job working for Alcatel in the mid 90s, then our unit was sold to Computeraid, a spin-off from Thorn EMI. After losing their shirt on Autonomy they were bought out by PinkRoccade, which was the privatised Dutch Civil Service IT and one of the largest employers in Holland, behind Phillips. Then Getronics bought out PinkRoccade.
Each move brought further disconnect from the business so I took a sideways step elsewhere...
"Didn't GCHQ essentially told parliament that they don't trust any networking gear from anybody or that any network could be deemed secure? An everything should be encrypted before it sent across any network?"
Is that not essentially paragraph 1 of any discussion on security that's worth its salt?!
The USP was supposedly that the software was more than just a search engine and would analyze/mine and give context to data and could do supposedly 'intelligent' search.
The company I worked for in the late 90s/early 2000s sunk a shitload of cash into a datacentre built in their head office in Farnborough ( go figure??? First mistake - it was prime office estate not nice and cheap industrial unit) to sell Autonomy as an early SaaS offering.
Like everything else that we were doing at the time that didn't involve box shifting or other throw it over the wall and forget business, our sales people didn't have a clue and it went nowhere. Pretty much broke the company and the net result was that we were bought out by a Dutch outfit called PinkRoccade.
You need to confirm by email by clicking on a link before your vote will be registered. Presumably only one vote per email address. I'd imagine it would be more than trivial to spam that significantly with bots.
I voted several hours ago but haven't had the email to be able to confirm. The total has only crept up by 100,000 odd in the last three hours. Wonder how many other people are still waiting for an email? Seems like a good way to knobble the process :-)
" I thought he was a police diver who'd taken a wrong turning while hunting for his misplaced flippers."
No police diver would be looking for his flippers because they call them fins. Flippers are for amateurs that don't know any better :-P
Strictly speaking, flippers are on water living mammals on the vestigial equivalent of their front legs
We had all the old crap in those machines. Apart from the 1st gen Sony CD drives ( complete with caddy ) that came in at about £400 a pop everything else was pretty long in the tooth for the early 90s - kyocera and various other 25Meg MFM drives, no-name wd1003 controller cards, various no-name MDA cards. If you were lucky you had a white screen monitor rather than the usual orange. Ahhh those were the days :-)
Sounds familiar :-) Our machines used to live on a shelf under the till counter and I think had Hayes or Akhter 1200 baud modems to transfer sales data back to head office. I think they shared the line with the phone on the counter so comms during shop hours couldn't be relied on, hence why updates were sent out on floppies!
In the early 90s I worked for a company who had systems in John Menzies shops ( UK high street newspaper, stationery, music, books, computer games seller ) across the country that produced copies of 8 bit home computer games on demand.
The system was just a 286 in a custom case with drives such as 3.5", 5.25", cassette drive and amstrad 3" in bays on the front, plus a bunch of blanked off spare bays for future expansion.
We used to send out updates on 3.5" floppy disk and the users were supposed to put the disk in the drive then select an update function from an admin menu in the system software and follow the prompts. Should be pretty simple but, when the first update went out we got lots of calls from shop staff saying they were getting disk not present errors or something like that.
After a lot of head scratching it turned out that they were forcing the disk into the gap between the drive bay blanking plates rather than into the drive itself!
It's a closed ecosystem so much of the water consumed will be re-cycled: water is broken down as part of the carbon fixing process (photosynthesis) but my guess is that the bulk of the water consumed is through transpiration, i.e. evaporation through the stomata pores in the leaves.
Usually, with embedded installs of SQL/Oracle/whatever database, there are no maintenance routines put in place so the system slowly grinds to a halt as the database(s) fill up, become fragmented, the filesystem fills up, etc, etc. Then you find out that all of the database access is via the system administrator account, with default passwords. This is especially true if you've paid consultants to come in and set it up who then don't have to support the system - throw it in and forget!
Biting the hand that feeds IT © 1998–2020