The y2k bug thread set me thinking. At the time I was touring Europe for Xerox hunting down not a Y2K bug, but rather a mystery bug where the billing routine didn't work in France or Germany or Italy but worked in the UK and other European countries. I tracked the problem down to the CVDate function in VB3, not functioning correctly when the decimal point character was a comma in regional settings. Indeed I was probably the first person to find this problem globally. I also then tested for Y2K related issues and found and fixed a whole heap of them and released this globally within Xerox. The Y2K team had missed this, so I greatly embarrassed them.
Years later I was working at the London metal exchange, I was only there for 7 weeks before I was bullied out by the developers. It all started when on my 2nd day the boss came in and all flustered as someone was able to place a trade before 8am which was illegal and potentially newsworthy. It was agreed it was a good task for the newbie to cut his teeth on, but I had to solve it fast. I was pointed to the VSS repo, and the 10k line stored procedure that was most likely the culprit. I set to work. 60 seconds later I had found and fixed.
The developer that wrote the proc said something like "that was far too fast". Several other times I was confronted for making the team look bad.
I was once described by a business analyst as "bordering on the savant", and a fellow contractor last year said I was "definitely somewhere on the spectrum".
I have recently been watching series 1 of House MD when it hit me. I'm the onery Dr Gregory House of IT.
Don't feel bad for the way you act towards me, it's perfectly natural.
Years later I was working at the London metal exchange, I was only there for 7 weeks before I was bullied out by the developers. It all started when on my 2nd day the boss came in and all flustered as someone was able to place a trade before 8am which was illegal and potentially newsworthy. It was agreed it was a good task for the newbie to cut his teeth on, but I had to solve it fast. I was pointed to the VSS repo, and the 10k line stored procedure that was most likely the culprit. I set to work. 60 seconds later I had found and fixed.
The developer that wrote the proc said something like "that was far too fast". Several other times I was confronted for making the team look bad.
I was once described by a business analyst as "bordering on the savant", and a fellow contractor last year said I was "definitely somewhere on the spectrum".
I have recently been watching series 1 of House MD when it hit me. I'm the onery Dr Gregory House of IT.
Don't feel bad for the way you act towards me, it's perfectly natural.
Comment