The problems with Genius Programmers

Are you suffering from headaches and high blood pressure? Then you may be working with a Genius Programmer


Warning: Genius Programmer at work. Steer clear.

REUTERS/Fatih Saribas

Once upon a time, early in my career, I took a programming job with a small web development shop. Not long after starting, I was informed that one of my fellow programmers was a GENIUS. Really, I asked, a GENIUS? Oh yes. VERY smart guy. Way smarter than the rest of us. We’re lucky to have him. As I soon found out, though, working with a GENIUS wasn’t quite the honor it was cracked up to be. In fact, it turned out to be a real headache.

I was reminded of this person (i.e., the repressed memories came flooding back) after an article in the New York Times about Brilliant Jerks. That article talked about brilliant people who can be very valuable when a startup is trying to get off the ground, then can turn into liabilities (and jerks) once the company finds its footing and begins to mature and grow out of the startup phase. The author speaks about the Brilliant Jerk from the point of view of a company principal (or consultant) who has the power or influence to do something about it.

Reading the article, I realized that I knew a close relative of the Brilliant Jerk - the Genius Programmer. In addition to the aforementioned GENIUS, I ran into this type of programmer now and again during my time in the coding trenches. Unlike the founder of a startup forced to deal with a Brilliant Jerk, though, it’s much different dealing with one of these types when you’re at an equal or lower level on the org chart.

While Genius Programmers are good at using their big brains to think deep thoughts, in my experience, they often have trouble working in a production environment. Why? Couple of reasons:

Lack of people skills - The classic nerd quality gets taken to a higher level with the Genius Programmer. They don’t communicate well (sure, they can opine at length on the root causes of the problems in the Middle East - or The Avengers - but don’t bother asking them to write usable documentation), they don’t listen well (your opinions are cute and all, but, seriously, <yawn>) and they always - always - know best. Why? Because that’s what they’ve been told forever.

Always rolling their own - Why use an existing product or tool that someone with a smaller brainpan wrote when you can create the next Mona Lisa in Perl?

Join us:






IT ManagementWhite Papers & Webcasts

See more White Papers | Webcasts

Answers - Powered by ITworld

Ask a Question