I once revoked my bosses e-mail and VPN access because his password was 'password123'. It was my job to keep things safe after all and I had asked him nicely a few times. EDIT: I proposed a new password of: @$tevezA$$ignedPwD@# (Steve's Assigned Password) He said no to that one.
Ask HN: What's the worst you've ever screwed up at work?
171–180 of 322 posts
Re: Ask HN: What's the worst you've ever screwed up at work?
#172I lost $7 million dollars in minutes by being short $700 million of US 2yr notes when the levees failed during the hurricane Katrina disaster.
Although my bet that the 2y point would be under pressure in the intermediate term turned out to be true, I got carried out by fund flows as folks spazzed out to cut risk by rolling into short duration high quality paper.
To his credit, my boss, who sat across from me, said only: "wouldn't want to be short 2 years." He let me make the call, which I did, and I covered my position. (Ouch.)
My book was up considerably on the year already, but this was a huge hit, and nearing year-end. I dialed back the risk of my portfolio and traded mostly convex instruments (options) for the remainder of the year.
Re: Ask HN: What's the worst you've ever screwed up at work?
#173I was working at a startup that was trying to create an affordable 3D printer. We had two working prototypes that were used for everything - demos, print testing, software testing, PR shoots, everything. Each prototype had cost hundreds of man hours to build and debug and quite a bit of cash as well.
Among other things I had done all the work on the thermal control system for the printer, it kept the print heads and build chamber at the correct temperature. One night while working on one of the printers I hit an edge case that my control code didn't handle well and the printer turned all of the heaters on full-bore. Half an hour all the plastics in the prototype had either melted or burned and I was left with a room full of smoke and a pile of scrap aluminum.
Re: Ask HN: What's the worst you've ever screwed up at work?
#174I've only cried literal tears once in the last ten years, over business. Due to inattention while coding during an apartment move, I pushed a change to Appointment Reminder which was poorly considered. It didn't cause any immediate problems and passed my test suites, but the upshot is it was a time bomb that would inevitably bring down the site's queue worker processes and keep them down. Lesson #1: Don't code when y…
> Fortuitously, AR didn't have all that many customers at the time, so only 15 or so people were affected. Less than fortuitously, those 15 folks had 10 to 100 messages queued, each. Excuse me for caviling at your post, but "fortuitously" is a synonym for "accidentally", not "fortunately".
Re: Ask HN: What's the worst you've ever screwed up at work?
#175Lesson: Keep the code that touches production databases as simple as possible so it's easy to verify exactly what it does. I was using a framework's database tooling incorrectly because I never dreamed what I used would touch the databases's counters.
(Not my worst mistake in terms of people affected, but it's the only mistake that was literally laser etched in metal forever.)
Re: Ask HN: What's the worst you've ever screwed up at work?
#176I was this close from setting the asset management server's hostname to `ASSMAN'
Re: Ask HN: What's the worst you've ever screwed up at work?
#177The PM brought the issue to the CTO, but somehow I didn't get fired. Ended up apologizing (obviously a poor choice of words :)) and moved on. Never made that infrastructure change.
Key takeaway: if you're going to talk shit, don't do so in writing. ;)
Re: Ask HN: What's the worst you've ever screwed up at work?
#178I've only cried literal tears once in the last ten years, over business. Due to inattention while coding during an apartment move, I pushed a change to Appointment Reminder which was poorly considered. It didn't cause any immediate problems and passed my test suites, but the upshot is it was a time bomb that would inevitably bring down the site's queue worker processes and keep them down. Lesson #1: Don't code when y…
Can't agree more with Patrick, mine is formulated a bit differently: Lesson #1: Don't push code on Friday afternoon. Lesson #2: Beer, Code and Commit is totally fine. Just don't push! Wait until next day to review and push/deploy it..
Re: Ask HN: What's the worst you've ever screwed up at work?
#179Back in my younger days, I once had a project manager who was asking me to make a significant network infrastructure change but refused to tell me why the change was necessary and basically told me to do as I was told. I messaged a coworker to see if he knew what was going on, and dropped in that the PM was being a "fucking cunt." I was unaware, however, that the co-worker and the PM were troubleshooting an issue tog…
Re: Ask HN: What's the worst you've ever screwed up at work?
#180i was the one developing the macromedia director app running on the cd.
we were on-time.
we were ready to send them out the door.
it was awesome.
and then we tested the rom outside of our network...
in some far-off corner of code, i had baked in a hard reference to one of our file servers on our network for some streaming assets. the cd failed as soon as you put it in the drive due to that reference to the missing file.
by the time we discovered this, we'd already glass-mastered and stamped 30,000 discs to the tune of $40k or so. or, about $6k per employee. in a company that booked about $50k the previous year. where i worked for free for 9 months.
so, my line of code cost our little company the equivalent of almost all of our previous year's revenue -- not profit, but revenue.
we, of course, had to make the run again -- only this time at the emergency rush prices. and this time, we were running late.
we managed to book some time in the middle of the night at the stamping plant. it was 4am. i had a courier standing over my shoulder watching me run the final build again, this time without the dreaded line of code -- which broke other things i had to fix when i removed it -- before he could take it.
i finished testing. ejected the disc. handed it to the courier, who started running as he was placing it into its case. he drove like hell to make it to the airport where we counter-to-countered it on a 2-hour, 6am flight to vegas for stamping.
oh, and it almost got even worse from there. almost.
we didn't know if they would be able to stuff the cds into the packaging because this was an emergency run and they didn't have the people available.
so...
we were actually on our way to rent a uhaul which we calculated we could drive to vegas just in time for the stamping run to finish. from there, we would load the discs on their spindles, and 4 of us were going to sit in the back of the van, stuffing 30,000 discs while we drove the uhaul to palo alto. from vegas. yes, stuffing discs in the back of a traveling uhaul.
we even had the patio furniture from one of the employees yards already picked out to sit in while we were in the back of the truck.
luckily, the plant managed to squeeze in our packaging (at rush pricing, of course) and all we needed to do was have one of our guys take them as luggage on a later flight that day to the bay area instead.
as to a couple, big lessons learned?
1) i can honestly tell you, i've never, ever had a hard-coded, local network link in anything i've shipped since and never will again. always test off-network. especially these days with mobile apps and their on-off-network states.
2) a strong, non-finger-pointing team is where you need to be. i felt appropriately awful, but we handled it as a team and proceeded to grow that little company to about $40 million a year before a merger.
p.s. oh, and next time, remind me to tell you about the time i ran a database query on production that nuked the entire website for the publicly-traded software company which relied on -- wait for it -- the website to do all its commerce.