News for hackers. Stuff that matters.
Re:Cause of today's Github outage by SkyMarshal on Sunday November 14, 2010 @10:42PM (#1905128)
> Exactly, I don't think you've really lived till you've experienced that pit of your stomach feeling when you realise you've just wiped out a product website / database.

Or sent a test email to thousands of customers in your prod database encouraging them to use web check-in for their non-existent flight tomorrow.

Yeah, did that five years ago, talk about heart-attack-inducing. Quickly remedied by sending a second email to the same test set, thankfully, but that's the kind of mistake you never forget.

Re:Cause of today's Github outage by lambda on Monday November 15, 2010 @12:56AM (#1905378)
Heck, you think that's heart attack inducing?

How about the DreamHost case in which they typed the wrong year in their billing code; charged many of their users for an extra year of service, to the tune of $7.5 million:

http://blog.dreamhost.com/2008/01/15/um-whoops/ http://blog.dreamhost.com/2008/01/16/the-aftermath/ http://blog.dreamhost.com/2008/01/17/the-final-update/

Re:Cause of today's Github outage by joelg87 on Monday November 15, 2010 @05:34AM (#1905877)
Wow. That is a great read.

“What’s the harm in keeping it flexible?” $7.5M in harm, that’s what! "flexibility" is rarely desired in programming!

Re:Cause of today's Github outage by resdirector on Sunday November 14, 2010 @11:54PM (#1905264)
I have a strict rule for myself: never use any curse words in any comments, variable names, dummy accounts etc.
Re:Cause of today's Github outage by jrockway on Monday November 15, 2010 @12:35AM (#1905343)
I have the opposite strict rule: use as many curse words in comments, variable names, and dummy accounts as possible. That way you'll find out quickly when someone else notices!
Re:Cause of today's Github outage by 1337p337 on Monday November 15, 2010 @03:43AM (#1905704)
I recommend against that. :) A team I was on had a demo for a client, and a shaky database schema. I had used, as a test account, the username "MOTHERFUCKINYEAH" for the same purpose. The purging of this account caused a few 500 errors, and we almost lost the client, and although I didn't get fired, we were all shuffled around after that to less critical projects, and one of us actually got sent out of the state.
Re:Cause of today's Github outage by 1337p337 on Monday November 15, 2010 @03:35AM (#1905694)
I don't think they're useful for variable names, but I use them (very sparingly) in comments. A great way to spot what needs refactoring is to find the piece that caused the most frustration to the author. Under a tight deadline, apologies to future maintainers can also be helpful in injecting some levity.