Owned by the Monkey

No Vijay, it’s not what you think.

Last night at about 9 PM I thought I’d sit down and work on a new feature and try a few more interface tricks I learned. The concept is pretty simple – make bookkeeping so easy everyone on the team can do it. Hopefully through the process more projects are handled to completion by the same member of the team, there are no drops in communication between the person that sold, the person that provisioned and the person that billed the customer. It might even make people more cognizant of how money comes into the company and how through just a few more clicks we can be that much more productive. So the natural thinking process is, once the order is completed (say upgraded quota, or new ExchangeDefender account or whatever) there should be just a few more clicks to update all the accounting. It already happens on the backend, but from time to time there are questions, mistakes.. This just cuts a lot of phone calls.

This is where I pwned myself. Looking back, its almost like a self-fulfilling Dilbert strip staring me, from start to finish. I’m coming up with stupid features, I’m designing them, and at about 2 AM cursing myself for the stupid idea to do this in the first place.

First, I decided to allow the admin to create billing objects on demand.

Then, I decided that those objects shouldn’t be fixed but dynamic and buildable on demand.

Long story short, I went from a few HTML input fields and a few SQL statements to a full blown table, form, validation and query designer.

My brain hurts. I wish I was dumber, at least I wouldn’t be going to bed at 4 AM.

3 comments on “Owned by the Monkey”

  1. Chris says:

    No, you are a caricature of a programmer. Program first, think second.

    A lazy programmer (OK, me!) would have doodled on a piece of paper and worked out what needed doing, then done it in the least amount of lines needed.

    But then it would have taken over a week, not 7 hours...

    What's the phrase - "a good plan today is better than a perfect plan tomorrow"?

    Besides, good sleep deprivation practice for Vlad (who knows, could still be Vladette!) Jr.

  2. vlad says:

    Totally. This has been on my mind for a while but I just finished some new code and was on fire to get it all implemented while I felt inspired.

    Maybe I'm in minority, but my development productivity sucks when I don't feel like coding and its easy to give up when it gets hard - as opposed to insane evenings when I just want to get things working bad enough that I'm up till 4 AM :)

    People like you are why deadlines slip and shit never gets done. People like me push out products that look like shit. We should hang together, maybe we could make one decent programmer out of the two :)

    Oh, and the kid is definitely a boy.. He didn't mind sharing that fact with us at all.

    -Vlad

  3. Chris says:

    When the inspiration is there, go with it.

    I guess it evens out in the end - the late night coding sessions irons out the slack days when the motivation isn't there.

    My programming foibles is probably the main reason I'm a sysadmin. But I do tend to produce flexible, maintainable code though, even though it takes a bit longer.

    We were told our first was going to be a boy. So it was a surprise when a girl popped out...

Historical discussion. New comments are closed for this post.