Okay, more from my Embarcadero blog. This is kind of becoming a greatest hits combined with a trip down memory lane. I particularly remember this conversation-turned-blog-entry. It was the result of a late-night, late-in-the-development cycle conversation that had us all laughing very, very hard.
- Okay — so I’m reading Steve Trefethen’s blog, and he links to what, in my personal opinion, is the greatest single title for a technical blog post ever —The Windows Shutdown Crapfest. Doesn’t get any better than that.
- So I read the thing, and it’s, well, amazing. They have a whole team of people that do nothing but work on the Start menu. That team had a whole team of people that works purely on the Shutdown experience.
- This fact above led to a discussion here on our release team about whether there is one guy on the C# compiler team who works only on the opening curly brace feature. Does he have pair programmer that works purely on the closing brace? When they work together, do they have to face each other? Does the Opening Curly Brace guy always have to sit on the left of the Closing Curly Brace guy? And what if Opening Curly Brace guy wants to keep working, but Closing Curly Brace guy wants to go home? Does this result in a syntax error? I have to know these things.
- Now, if you think the above sounds ridiculous, then I think you’d should actually read the whole article. It’s an amazing tale of Kafka-esque development processes. Dude had to wait up to three months for his code to actually reach the product.
- And I thought that we had a convoluted release process here.
- Yes, we are getting a little giddy.
(Note: this blog post was written by a committee).