When a critical service goes down, what happens to your apps? Do they go down too? Should they? Or should we plan for the service not being available? My team's experiences dealing with a major crash left us asking these questions. The Crash Just after lunch this past Thursday, my
A junior programmer (let's call him Luis) and I were working to find a particularly stubborn Heisenbug [http://en.m.wikipedia.org/wiki/Heisenbug] (a bug that seems to disappear when you attempt to study it) this last week, and it was kicking our collective butts. This thing was just
I was able to find the nest, to my knowledge the first hunter to do so, before the Glitch nearly ended me. This bug is the most elusive I've ever tracked. I'd been following it's trail for days, watching its movements, trying to determine exactly where the nest was located.
LISTEN UP RECRUITS! This is Good Code Basic Training! I'm Sergeant Soccly, and it's my job to get you newbies up to speed on the problems this profession faces so that you can be prepared to deal with them. Our mission is to fight the evils of bad code design,
> The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. > - The 90-90 Rule [http://en.wikipedia.org/wiki/Ninety-ninety_rule], proposed by Tom Cargill There's a classic, constant pull