Low Frustration Tolerance: Curse and Blessing

There's a psychicologicalous condition known as 'Low Frustration Tolerance', (LFT for short... abbreviations, btw, are helpful for those with LFT ;-))

Low. Frustration. Tolerance. I am writing slowly. Just to frustrate the Living Hell out of those who have LFT.

Every day you will see examples of people with Low Frustration Tolerance. You know these people.

You're in your car, stopped at the lights. Light turns green, and before you've put your foot on the accelerator, the guy behind you blares on his horn. Hard. He's got LFT. Bet on it.

To be a programmer REQUIRES a ^^high^^ level of frustration tolerance. Most people with LFT, on the other hand (OTOH ;->) end up as drunks, hobos, drop outs, early-deaths, burn-outs.

(But stick around -- there is a twist.)

So, the only way to be a decent programmer, able to produce good output every single day is to have a high-frustration-tolerance.

The amount of frustration we encounter in the computing world, every single day, is just astounding. Many days our job consists of leaping one hurdle after another.

Sometimes, just for fun, I keep a little log of the hurdles I encounter in a day. They are numerous.

I want to get from A to B. Step A: Something goes wrong. I investigate. Dead end. I google it. Dead end. I check logs. Dead end. I increase logging. More evidence. I google that. Dead end. I download a tool that will get more info. Tool fails to install. I google the installation failure. Dead end. I look for another tool, install that, run it: crashes. I investigate the crash. Dead end. I find a different tool, install that. Get more info. Investigate that. Dead end. Google it. Dead end. Stack overflow it: dead end. Drink coffee, consider taking up smoking. Dead end. Wait two weeks, increase bounty at stack overflow. Dead end. Reboot, check patch level, look for random hints from astrological tables, listen to reggae... dread end. Sometime later, randomly: breakthrough. And on step B.

Annnyway, I've established the first point: a good career in programming requires High Frustration Tolerance.

And yet... I am utterly convinced, that the only way to succeed as a programmer is to have really LOW frustration tolerance.

You have to get fired up by tiny little things. You have to care, dammit, and care deeply, about tiny little points.

You have to pour your heart and your soul into accepting nothing but perfection from that damn regular expression, that damn CSS selector, that damn SQL case statement, that bloody mother f***ing a*****e of a *** **** son of a ******* ugly ***** ***** **** of a **** installation package, so the lucky ******* **** of an end user gets all the joy of a working system.

It's a catch 22.

And sometimes we forget that *both* skills are needed. We fall into the trap of being one or the other.

So here's my latest plea:

Stopping being so easily frustrated. And please, stop settling for second best.

And then: tell me how it's done.

I'm thinking the correct combo should be a "High" frustration tolerance with just enough OCD (Obsessive Compulsive Disorder) to get the little stuff right, er, Perfect!

I've never commented before, but I just had to for this. This article describes my life!! Thanks for the laugh; I just stayed up a whole day and night troubleshooting a problem, so I needed it.

I'm frustrated with having to type meatbag to post a comment.

And I look a lot like the programmer pictured in the top right of this post.

Help me.

Once again, a very insightful article.

My current project has my frustration level very high, but I have to switch into high tolerance mode in order to get things done by a hard deadline.

This makes me think that while a good programmer requires both HFT and LFT ... a _really_ good programmer needs to be able to switch between the two at will.

@Matt et al
I think Mike hit the nail on the head (above):

>"High" frustration tolerance with just
>enough OCD to get the little stuff right

Really amusing and spot on.

One resolution à la Postel's Law: high tolerance for the frustration one encounters (at the hands of oneself and others), low tolerance for the frustration one engenders (unto oneself and others).

Another resolution: high tolerance is good insofar as it causes you to keep going (and not going postal), low tolerance is good insofar as it causes you to make things better.

In either guise, HFT and LFT are eminently compatible.

It also helps if you can tell what matters. Some things aren't worth getting all perfectionist over, some are. :)

You neglected to mention the endless frustration of having to strongly rely on tools which crash or freeze or otherwise bug out on you multiple times a day. Like, say, Visual Studio 2008.

That explains a lot. Ah! Do me a favor and... when someone tells you how it's done, forward the solution to me... My FT is getting L :)

The ideal programmer has a LFT with a very low FRL (Frustration Reset Level) and a LER (Low Escalation Rate).

Basically you encounter a problem. You're instantly frustrated and look for a solution.
You find a hint at a solution (You reset your frustration level to Zero or your FRL has been hit). Then your hint reveals it's not a solution (Dead End). You get instantly frustrated again.

You hit a dead end trying for alternative with no further hints. You get more Frustrated. (Normal people start getting irritated then angry). Ideal programmers however barely increase their frustration level. Due to LER, road blocks and increasing difficulty stopping the frustration doesn't really get you more frustrated at a actively observable rate. (not that you don't get more frustrated and would definitely be seen to be so after a week or two of continuously increased frustrations.)

Another great post lb.

HFT and LFT go hand in hand every single day of my programming life.

Knowing when and where to apply each is where most plebians fail. The good coders have the ability to pick it, the bad ones dont.

You need to have a LFT. Definitely. Surely, the geek thing is more about how you express that frustration. We get frustrated, and start pushing stack until we get to a root cause that doesn't frustrate us. Then we pop our way back all the way down to the original frustration point, and kick it's sorry ass all the way down the street.

Frustration? What frustration?

LFT is just what we need, not only for regular person, but especially for programmers. Thanks for making a burst of laugh:-)

writing a log about the divide and conquer process. That's good, I'm stealing it.

consider those who must say "may i help you?" more than 999 times per 8 hour shift. that's what i do. talk about repetitive motion problems. this is no exaggeration on the amount of people i handle each shift. of course, i must also be a multi-tasker too. thank your great binary gods that you don't have the people problem too.

my monitor has what i perceive to be a short, chubby 'neck' i have often placed my two hands around the neck while talking sweetly to a customer.

Low Frustration Tolerance: Curse and Blessing

NimbleText is a Powerful FREE Tool

Articles

Twitter, baby

Recommended Reading

Recommended blogs

Aggregated Links

Human Link Machines