Kommandeering Developers Everywhere

Friday, June 23, 2006

It's a simple 19-step process

Years ago, in a fairly large software development effort, my group had some internally modified 'make' system for code that worked just fine and was pretty efficient.

Of course, that meant someone had to tamper with it. In a quest for elegance and a couple of features that no one in their right mind would ever use, someone on our vaunted architecture team introduced a new series of steps to check out, check in, and build our code. I immediately dubbed this nefarious turn of events by its rightful name: "The Simple 19-Step Process." Why check out and check in when you can execute 19 steps manually instead?

Why am I telling this story? Because of this link.

Are the steps correct? Can they be improved upon? Should people be thankful that such a page exists? Can you read every step and shrug in its simplicity? Should complex steps involving complex software be forcefully made simple, sometimes too simple? Can and will those steps be improved or automated?

None of these questions are the questions you should be asking. Most people would have a better chance of solving a Rubik's Cube with their feet than even copy/pasting those instructions to their command line.

Sometimes, you have to have faith in your abilities and keep your self-esteem in check. If you can admit to manscaping, you can admit that "Next->Next->Finish" isn't always evil.


Post a Comment

Subscribe to Post Comments [Atom]

<< Home