I have good-coding days and bad-coding days. And all it takes is a touch of distressing code to send me over to the dark side. Granted…an accomplishment always sends me back.

I’d been working on my own little program. For those of you that know my coding this is, “Yet another dev project….’ Though this one has gone exceedingly better than others have.

Meanwhile, at work I’ve been asked to add functionality that I’ve advised against. What developer hasn’t found himself in this little box? Well, I soent a good 2 1/2 hours last night expending lots of clever points. Making something work that just shouldn’t. Today when I presented my findings to the great old ones. The architects….

Unfortunately, I didn’t expend nearly enough clever points and it would seem that some of the work was already done for me and in a manner that is more complete and better handled.

And on days like this I wonder why I haven’t returned to theatre.

Edit: 20061125 – Adding tags and elabouration
Added: 20061125 – I wish I could tell which coding project this was. Over the years there have been many. One of my older ones actually came around again recently (the Life program).

As for the work issue. I believe this was an application I was designing at Symantec. The Application was about 95% UI and 5% code. I think I talk about this later, but in the event that I don’t:

When designing a program, most people stay away. Algorithms scare people. UI on the other hand is different. Everyone thinks they are a UI engineer and will tell you how the program should be written. In this case, I had a PM decide that he knew how the program should work. When I told him it wouldn’t work that way, he went to one of the architects and asked them for code. He then presented me with the code he’d acquired to, “do it his way.” I was insulted. My manager looked like he was ready to deck the PM.

I really did enjoy my time at Symantec. We just suffered from ‘red-haired, bastard, step-son’ syndrome there.

« »