|Not bad for a greenhorn
||[Mar. 6th, 2009|01:28 am]
Just for a bit of background: In work, there's a tool we use that's central to our work. It schedules our tests, and tries to find a way to run all the tests we want to run in a reasonable amount of time. It is the most sophisticated harness I have come across. The way we sell it to other groups in work, you'd think it would cure cancer. For the most part it does what it was intended to do.
However, from a programmer's point of view, it's like Michaelangelo's David made out of string cheese. From a distance, it's a work of art. The closer you get, the you start to see it for the mass of sinuous dairy product that it is. One could argue until one was blue in the face as to whether the fact that it's pieced together so tenuously from such improbable materials makes it more worthy of appreciation as art or not. Ok, it's not that bad, but for the techies let's just say it's mostly /bin/sh, perl and expect.
Now, these days, we have some folks in Prague who are very interested in its development, and the two teams work more or less independently of each other to improve the bits we need. Unfortunately, when you have two relatively large teams working independently on something like this, you're going to step on the toes of others. So, an ARC (architecture review committee) was proposed, which is basically a committee of developers familiar with the product who will steer future design decisions so that we can co-ordinate our actions better.
I was asked yesterday if I wanted to be on the ARC which, given the fact that I'm a 4-month greenhorn, surprised me. After a quick chat to my Team Lead, and deciding it couldn't hurt my career or anything else, I'm now a committee member; I have a vote as to how our main tool is crafted.
Seriously though, committee-ism is like malaria, once it's in the blood, it's likely to resurface and strike at the most inopportune moments, like now. On the other hand, it means I get to develop a proper working relationship with the Czech guys.