Its expensive to fix it late!

So there was an Engineering all-hands this week. Constantine took everybody through a bunch of metrics on the cost of bugs in production and having to fix the stuff our customers find. It was mega-scary, it was like an exponential multiplier at each later stage in the process to fix the bug. Wow that gets expensive!

Other places I have worked you hold the release until its ready and then push it. We use a different method here, its Tuesday so we push period. I though this was super agile, until I saw the facts of the cost of fixing bugs rather than holding the release. I get the fact that we have customer commitments, but wouldn't they want the release to be late and working than on time and full of bugs? Now I see that we could have employed a dozen more people (or not let a dozen people go). I see the faults in the process. What we have is bogus despite what the "old-timers" say. That includes Can-I-Have-A-Latte-Sire, Stacy and Lonely-James.

I talked to Dave (Chief Architect) afterward and he said "Its sucks, but its so much better than we had a YahBay". I say that's not good enough, we need to be better than everybody if we are to be the next big story. YahBay are dead, Hank Commerce will live long into the shared internet memory.

This weeks food and drink
Beer : 0 (no more official drinking!))
Shots : 0 (no more official drinking!)
Dinner : 0 nights (no more dinners!)
Weight : 179 lbs