This Developer's Life 2.0.2 - Pressure
In this second episode of the second season of This Developer's Life we talk to a group of Top Gun developers: the StackOverflow team, about the day their database melted - and how the team responded.
- Geoff Dalgas - developer on StackOverflow
- Sam Saffron - developer and data geek at StackOverflow
- Jeff Atwood ,Mr. CodingHorror and co-founder of StackOverflow
Also, please visit the new site at http://thisdeveloperslife.com. We've got sixteen episodes so far, and we are pretty proud of them. Don't listen to podcasts? Don't commute? Surely you have a long plane flight coming up? Maybe a cross country drive? Load up. It's all free.
You can download the MP3 here (53 minutes) and visit our site at http://thisdeveloperslife.com.
Please consider subscribing with iTunes, or Zune. If you enjoy it, take a moment and please do REVIEW our show on iTunes.
Or if you have a BitTorrent client and would like to help save us bandwidth money, as well as the bragging rights of downloading legal torrents via RSS, get our Torrent Feed at ClearBits.
The bandwidth and other costs for this week's show were picked up DevExpress and CodeRush! Visit them and thank them on Twitter.
This Developer's Life is brought to you by CodeRush for Visual Studio.
Announcing our listener contest...This Developer's Life - Crowdsourced
Oh yes. We want to hear your stories. Record your best developer stories and send them to us and if we think they rock, we'll include them in the next episode of This Developer's Life.
What we need from you:
- Your story. We don't want interviews, we want stories. Tell us about your passion, or something crazy that happened at work while solving some technical problem.
- Keep your audio clean. Use a decent microphone or at least make sure you don't "overdrive" your microphone by talking to close or two loudly. Don't record while mowing the lawn and don't record in a giant echo chamber.
- Be passionate. Talk to us like you're talking to a friend.
- Don't worry about editing or music. Just share. We'll handle the Lady Gaga mashups.
- Note we may move your audio around or change the order of stuff to make it more listenable or interesting or both.
- Change the names of companies and people to protect the innocent (or guilty)
- Know that by giving us your audio you're releasing it the Creative Commons and that we may or may not use it for a future show.
Send us a link to your audio file and what you're talking about and we'll do the rest. See you next time!
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
We tried to recover our corrupt db file and were unable to get it to a steady state, within an hour we decided to go with the backup, I then used the corrupt db as a source and sucked in all the information into the good / live db. It was tricky, I had to deal with remapping cascades of identity at 3am my time. Still objectively we are talking a few hundred posts on a free website, its not like lives would be lost if I messed up, or planes would crash. Still on a personal note there was heavy pressure.
It's tricky, the podcast deals with the emotions and story, its less about being a lesson for other dba out there.
This would not be such an issue, but all of the locations I can get the MP3 from are blocked by my employer, so I would like to torrent the MP3 to my home computer, then FTP it from there.
Thanks.
Comments are closed.
My overall feedback is it would have been nice to at least mention the fact that there are financial consequences to downtime and data loss, and they need to be weighed vs. the time and effort to recover. I suspect that a decision making process not colored by the pride or ego factors of showing other programmers that you can recover from even the most heinous database corruption, but rather on strict financial cost/benefits, would have led to a decision to restore the backup and get the ad revenue flowing again ASAP rather than take the downtime to recover the lost Q&A data.