in reply to Programmer's Frustration

What is frustrating in this thankless profession? Let me count the ways...

Actually if I didn't Love what I do I never would have made it this far. It is the creative & thought provoking aspect that has me hooked. There is nothing like the pride of creating a functioning somethingorother out of electrons & ideas.

But I think probably the Most Frustrating experience, (aside from endlessly being forced to take shortcuts to make short term savings which are costly in the long run by managers whom don't understand exactly what it is That I Do...) would probably be my experience with Extreme Programming.

Why? Simple. The concept of sitting two guys down at a single desk and computer to write code may be more productive, but it leads to burnout much faster.. And with regards to what you mentioned about smelly (i.e.BO) coworkers...ACK! And if you don't like them it gets worse. I don't need to smell what co-workers had for breakfast to be productive.

So how do I cope?

When I get truly bent I stop working & go on PerlMonks :-)

At lunchtime I would NOT eat with my coworkers. I'd go for a walk, get some fresh air & restore my personal space.

And then when I get home I sit down at my workstation & get some real work done.

Thank Bhudda I don't have to deal with that anymore...



Wait! This isn't a Parachute, this is a Backpack!

Replies are listed 'Best First'.
Re: Re: Programmer's Frustration
by infoninja (Friar) on Apr 16, 2001 at 19:17 UTC
    I'm in a (mostly) pair programming environment, and I've found my (our?) productivity is much higher, and frustration level much lower, when we're pair programming. Of course, that's probably also heavily influenced by the fact that we were friends before we started working together...
Re: Re: Programmer's Frustration
by gregor42 (Parson) on Apr 16, 2001 at 19:29 UTC

    I'm not trying to smear Extreme Programming, because it can lead to tremendous learning increases by sharing coding styles & algorythms.

    But at the risk of perpetuating a stereotype, most programmers (@ least hard core) tend to be somewhat lacking in social skills. Myself Included.

    To that end I personally prefer a prelimminary brainstorming session & later a code review process to go over what's been done. I think this can have the same benefits overall, except perhaps that you need to actually BUY a computer for every programmer. 8-P

    Another frustration issue...Why do programmers always get lame gear? (And don't give me that crap that your code should run on EVERY machine...i.e. lowest common denominator)



    Wait! This isn't a Parachute, this is a Backpack!