However, there are times this is not true, we as programmers usually get stuck with something that is complicated to solve.
That might be a bug, a non-trivial problem that we need to solve, or whatever it might be that we cannot solve quickly.
How do you deal with the stress though?
The only thing I do when feeling stressed, is to physically step back. I walk away from the computer, go on on a run, or get some sleep.
It is often within this absence that the solution to my programming problem emerges.
And then you get real stress.
That's what I'm referring to, how do you deal with that?
I'm not saying I don't enjoy challenges of solving real problems with programming, I do enjoy them.
As I get more experienced I get stuck or encounter problems less and less, I think I just keep doing more challenging or unfamiliar work in order to keep chasing that high.
I'm saying, how do you deal with stress of tight schedules and deadlines AND having to solve a hard programming problem.
(1) Backing away. Pushing through stressed produces inferior results.
(2) Using a different constraint. That's the real trick.
Only I can't make myself pick the right constraint from the get go if I'm feeling stressed, so I stay stuck in a loop. I need to back away for the subconscious to reveal the right constraint.
It's as if I have to give up first. It seems it's only then I finally let myself attempt a solution I haven't tried before.
So ironically the way to deal with the stress of getting stuck and having deadlines is to manage to reach the point where, after trying everything, you sincerely no longer give a damn.
But mix that with the pressure from your employer and deadlines and you get even more stress.
This is what I'm referring to.
How do you deal with that?
From the simpsons... Hank Scorpio: I'm gonna leave everything to you. We're on a tight schedule. You keep them motivated. [he leaves] [his staff is busily working] Homer: [to staff] Are you guys working? Man 1: Yes, sir, Mr. Simpson. Homer: Could you, um... work any harder than this? Man 2: Sure thing, boss. [they do]
Also relevant if your self-employed. In that case you must not be creating realistic schedules for yourself.
If I'm doing some project with a hard real deadline say, 3 months away. I'll arrange my timetable to have everything completely finished at least a week early cus I know, something or other will crop up at end end.
In conclusion perhaps scheduling/planning/timetabling issues are the route cause here. If you arent self employed you should definitely bring this up with your employer. If they are even halfway decent they should take this very seriously.
ps. I've only been working in software for a few years now but I have a good few years of experience working as an architect (building buildings) Architecture is all about project management and stuff always goes wrong! + If you delay the project everyone sues your ass off!!
What I do varies based on the situation… but one of the most surefire ways of making headway through difficulty or just frustration is pair programming.