Programmers under pressure

by Vukoje 28. February 2010

In my previous blog post I have mentioned that most of our job candidates state in their CV-s that they work great under pressure. The thing is ... nobody works grate under pressure. The only difference between people is whether they break under pressure or not.


The pressure is something well known to probably every programmer, but hopefully it isn't present every day. When I say pressure, I don’t think of managers forcing programmers to code for long hours. I rather think about situations when you must finish something that you care about very much, but the situation makes it almost impossible.
This is often the truth for developers because we:

  • have deadlines,
  • do complicated things that are error prone,
  • lack engineering practices and tend to throw the ones we got the first time we hit the wall


Because pressure is probably guaranteed thing, first thing we can do is become aware of it. I have met two kinds of pressure: negative and positive.

Negative pressure


This pressure emerges once you start to break your deadlines only to find out that your solution didn't satisfy customer requirements. The code is very bad, there are problems everywhere and everybody is pushing the problems under the rug because there is too much of them. Nobody can get anything done because of the piled up impediments and codebase that have become super complex and meaningless. Even when you get something done, you later find out that some existing functionality was broken by your changes. You wake up in the morning sick of thinking you are going to the same unsolvable problems again. At the end the tension between teammates becomes evident because someone must be quality for this state. Is it the programmers, the testers, the managers?

The only positive thing in this situation is that you will learn many things that you shouldn't do as a programmer because they will come back to bite you. Also you will have a scary story up your sleeve that can come in handy when you need to dramatize bad practices that could cause another project to get in this state. Until this state becomes just an anecdote, listen to Freddie Mercury's advice, it may help.

 

Positive pressure


Negative pressure is pretty obvious with its causes and side effects, but positive pressure is something much more subtle and hidden. It happens in opposite situations, when group of people has a big challenging goal ahead of them. This is never an easy task but everyone is doing the best they can. You could say that everyone is striving for perfection. Because perfection is impossible and mistakes are happening, the positive pressure emerges.

When people in these situations are really really dong the best they can, thinking of the challenging problems when they go home, trying to help everyone, they become very tired and sensitive. If they feel that their efforts are unappreciated they will be devastated. The more everyone is committed the more likely they will neglect this social component of successful projects.

As you can see, there is no real problem here, because this is only a slight problem in communication, but with possible serious outcomes. So if you identify positive pressure, talk about it with your collages and say how much you appreciate their work. Everyone will feel that they are fighting on the right side again and keep doing the best they can.

Tags:

management

Comments

2/28/2010 6:02:11 PM #

Vukoje.NET | Programmers under pressure

You've been kicked (a good thing) - Trackback from DotNetKicks.com

DotNetKicks.com

3/1/2010 11:15:40 AM #

I've been reading a little more on technical debt and, to me, when you create the right type of technical debt you can create positive pressure (this implies that the lines of communication are strong) whereas when you have th ewrong type of pressure, your communications are strained and you head into that spiral known as the big ball of mud (or worse).

allison perkel

5/11/2010 4:54:41 AM #

I came looking for consolation when i was under presure to debug code that was written  by other programmers. my boss thinks i can do everything which is wrong. even doctors dont cure everybody but do some some refers. pew!

kalya

1/14/2013 2:57:57 AM #

This SAVED my webworks apps!!!

thomas

Add comment




biuquote
  • Comment
  • Preview
Loading



RecentComments

Comment RSS

Webcom

 

 

 

 


Soprex