TechRepublic : A ZDNet Tech Community

10 Things

Host: Jody Gilbert, Senior Editor
Contact

Programmers make big bucks. Software developers dress casual every day of the week. Anyone can teach themselves to be a programmer. These are just a few of the reasons why people say they want to become a developer. Unfortunately, the job market is littered with people who may have had the raw intelligence or maybe even the knowledge, but not the right attitude or personality to become a good programmer. Here are a few things to consider when deciding whether you should become a software developer.

Note: This information is also available as a PDF download.

#1: You’d rather be trained than self-teach

In most development shops, there is rarely any training, even if the company has a training program in place for other employees. At best, the company might reimburse you for a book you buy. Programmers are expected to arrive on their first day with all (or at least most ) of the skills they need. Even worse, the assumption is that programmers are really smart people who are good at problem solving. That assumption leads upper management to believe that good programmers do not need training. Finally, training for developers is extremely expensive. The result? When you change positions, you will need to figure out what is going on yourself, and you will probably need to teach yourself.

#2: You like regular working hours

Software development projects are notorious for being late. Even the projects that are delivered on time always seem to run behind schedule at some point. If you don’t like (or can’t handle) irregular or fluctuating demands on your time by your employer, development is not for you. When crunch time comes, your employer is more concerned with getting the product in the hands of a million-dollar client than with your child’s soccer game or the new TV program you wanted to watch.

#3: You prefer regular raises to job-hopping

The world of development is one of continual erosion of skill value. Unless you are working at a shop that deals with slow-to-change technologies, chances are, your skill set is less valuable every day. The state of the art is changing rapidly, and the skills that are hot today will be ho-hum tomorrow. As a result, it is difficult to sit at the same desk doing the same work every day and expect a raise that exceeds a cost of living increase. You need to keep your skills up to date just to maintain your current value. In addition, if you want to boost your paycheck, you need to expand your skill set significantly and either earn an internal promotion or go to another company.

#4: You do not get along well with others

It’s one thing to be an introverted person or to prefer to work by yourself. It’s another thing to be unable to get along with others, and it can sink you as a developer. Not only that, your manager may well be a nontechnical person (or a technical person who has not worked hands-on in some time), so you need to be able to express yourself to nontechnical people.

#5: You are easily frustrated

Software development is often quite frustrating. Documentation is outdated or wrong, the previous programmer wrote unreadable code, the boss has rules to follow that make no sense… the list is endless. At the end of the day, no one wants to be working next to someone who is always cursing under his or her breath or screaming at the monitor. If you are the kind of person who goes insane spending eight hours to do what appears to be 10 minutes’ worth of work, this is not a career for you.

#6: You are close-minded to others’ ideas

In programming, there are often problems that have only more than one “right” answer.  [Update: Corrected by author] If you do not handle criticism well, or do not care to hear the suggestions of others, you might miss something important. For example, a few weeks ago, one of our junior-level people made a suggestion to me. After considering it for a bit, I decided to try it. It turned out that he was right and I was wrong, and his suggestion brought the time to execute a piece of code from multiple days to a few hours. Ignoring this person due to the difference in our experience levels would have been foolish.

#7: You are not a “details person”

Programming is all about the details. If you get lost in a movie more complex than Conan the Barbarian or have a hard time filling out a rebate voucher, you probably won’t do very well in the development world. Sometimes, something as simple as a missing period can mean the difference between random failure and perfect success. If you are the type of person who might not figure out where the missing period is, your career will be limited in range, at best.

#8: You do not take personal pride in your work

Sure, it’s possible to program by the book and do a passable job. The problem is, the book keeps getting rewritten. Software development is not a factory job where you tighten the same bolt all day long, where a touch too much or too little torque makes no difference. It requires independent thought, which in turn requires the people doing the work to take pride in it. Furthermore, it’s easy to do something the wrong way and have it work just well enough to end up in production. That “little error” you turn a blind eye to since it doesn’t seem to cause any problems will cause problems. Programmers who do not treat each project as something to be proud of turn out poor quality work, which in turn makes their careers short-lived.

#9: You prefer to shoot first and ask questions later

Software developers, at least the good ones, spend a lot more time planning what they’re going to type than actually typing. Usually, when coders just open up their code editor and start banging away at the keyboard, most of what they write gets ripped out later. Programmers who ponder, think, consider, and plan write better code in less time with fewer problems. There’s a reason so many programmers barely know how to type properly: The hard part of the job is knowing what to type. People who do not invest the time up front in their zeal to get started with the “real work” are actually skimping on the “real work.” If you are a doer and not a thinker, software development is probably not a good career choice for you.

#10: You do not like the geek type of person

For a bunch of reasons (some legitimate), a lot of people just do not enjoy being around the engineer or techie personality. If you have a hard time with the Dilbert or Weird Al personality type, do not even consider going into programming. Are all developers like that? Of course not. But they comprise a large enough portion of the workforce that you would be miserable in the industry.

Justin JamesJustin James is an employee of Levit & James, Inc. in a multi-disciplinary role that combines programming, network management, and systems administration. He has been blogging at TechRepublic since 2005. Read his full bio and profile.

Print/View all Posts Comments on this blog

GREAT ARTICLE zoldello@... | 10/23/07
Be unwilling to compromise when it will affect supportability or quality. F4A6Pilot@... | 10/30/07
Reread the "get on well with others" part erwin_glassee@... | 11/07/07
Fairly accurate Tony Hopkinson | 10/23/07
Tony, I think Jaqui | 10/24/07
I was taking best as right myself Tony Hopkinson | 10/24/07
exactly. ~nt~ Jaqui | 10/24/07
One Right Way CodeBubba | 10/24/07
"only one 'right' answer" news-shop@... | 10/24/07
I'm pretty sure Jaqui | 10/24/07
Embarrassing typo! Justin James | 10/24/07
RE: 10 signs that you aren't cut out to be a developer DPeek | 10/24/07
Lot's of people did it during the last boom Tony Hopkinson | 10/24/07
Yup Justin James | 10/24/07
Re: Yup Bad Boys Drive Audi | 10/31/07
RE: 10 signs that you aren't cut out to be a developer judexy22@... | 10/24/07
Judex, Jaqui | 10/24/07
I'm pretty much completely self taught Tony Hopkinson | 10/24/07
Expected Mentoring, Not Training JohnnySacks | 10/24/07
Never had a mentor. Tony Hopkinson | 10/24/07
Mentoring is important a.haskell@... | 10/29/07
I agree Justin James | 10/29/07
Mentoring us 20 somethings TJ111 | 10/29/07
Putting it into words Justin James | 10/29/07
When I've done mentoring, Tony Hopkinson | 10/29/07
The Problem with Education Bad Boys Drive Audi | 10/31/07
I learn and have learnt from putting Tony Hopkinson | 10/31/07
Or... Bad Boys Drive Audi | 11/05/07
Twenty plus years has given me a bag full of mistakes Tony Hopkinson | 11/05/07
I agree Justin James | 11/01/07
The ways of life erwin_glassee@... | 11/07/07
RE: 10 signs that you aren't cut out to be a developer john_ludlow@... | 10/24/07
Working OT / Weird Hours CodeBubba | 10/24/07
OT is for suckers SnoopDougEDoug | 10/24/07
Six years of contracting Tony Hopkinson | 10/24/07
I agree Justin James | 10/25/07
RE: 10 signs that you aren't cut out to be a developer klemen@... | 10/24/07
Prefer Regular Raises to Job Hopping... Stan.Williams@... | 10/24/07
Productivity SnoopDougEDoug | 10/24/07
I don't think so KeeBored | 10/29/07
Other reasons you may not be out to be a developer Web-Guy | 10/24/07
RE: 10 signs that you aren't cut out to be a developer Tell It Like I See It | 10/24/07
I agree that alaniane@... | 10/29/07
Yes, indeed Justin James | 10/29/07
Another Top 10 list to help... jreddy@... | 10/24/07
Well aside Tony Hopkinson | 10/24/07
Kids Justin James | 10/25/07
#11 don.gulledge@... | 10/24/07
RE: 10 signs that you aren't cut out to be a developer DigitalFrog | 10/24/07
RE: 10 signs that you aren't cut out to be a developer Office Mole | 10/24/07
RE: 10 signs - A good 10 list for a change. rkendsley | 10/24/07
Thanks for the kind words! Justin James | 10/25/07
RE: 10 signs that you aren't cut out to be a developer Avner_Uzan@... | 10/24/07
I especially disagree with #9 mydoghasworms | 10/24/07
Disagree with #2 especially if you are #9 type kpthottam@... | 10/24/07
+/- 40hrs over 6 months ? Tony Hopkinson | 10/24/07
Are you actually a developer or just a code grinder? DigitalFrog | 10/25/07
I'm expecting him to put in a link Tony Hopkinson | 10/25/07
It is called modelling...something us older folk called design kpthottam@... | 10/29/07
Well congratualtions Tony Hopkinson | 10/29/07
Trained Monkeys are Offended jk2001 | 10/26/07
so what zoldello@... | 10/28/07
concur with comment-- Artists plan and engineer results kpthottam@... | 10/29/07
Model driven Architecture & Model driven development kpthottam@... | 10/29/07
The problem is alaniane@... | 10/29/07
A lot of truth to that alaniane jreddy@... | 10/30/07
Well yes, I would n't advise holding your breath though Tony Hopkinson | 10/29/07
on the fence zoldello@... | 10/28/07
#11:YOU DON'T WANT TO SELL YOUR SOUL TO THE DEVIL. BALTHOR | 10/25/07
No reason to sell your soul john@... | 10/29/07
MAKE A BOOK CHAPTER zoldello@... | 10/28/07
Thanks! Justin James | 10/29/07
You should KeeBored | 11/04/07
RE: 10 signs that you aren't cut out to be a developer DRAGON53532000@... | 10/28/07
RE: 10 signs that you aren't cut out to be a developer gmiller@... | 10/29/07
RE: 10 signs that you aren't cut out to be a developer SnoopDougEDoug | 10/29/07
More.. Hollywood also says you aren't cut out to be a developer if Former Big Iron Guy | 10/29/07
Law & Order Justin James | 10/29/07
LOL good one Sir! Locrian_Lyric | 10/31/07
Argh! Justin James | 10/29/07
Hit the nail on the head ByteBin | 10/29/07
Well Organised ???? Tony Hopkinson | 10/29/07
Not THAT Tidy! ByteBin | 10/30/07
I consider a comment Tony Hopkinson | 10/30/07
I dunno... john_ludlow@... | 10/31/07
Meaningful comments Tony Hopkinson | 10/31/07
Here is why I like comments so much ByteBin | 11/02/07
WIP notes in the code Tony Hopkinson | 11/02/07
I disagree again, lol KeeBored | 11/04/07
I disagree KeeBored | 11/04/07
I prefer type three myself Tony Hopkinson | 11/05/07
True that KeeBored | 11/05/07
I guess I come across as type 2 john_ludlow@... | 11/06/07
Developing is an art mikes@... | 10/29/07
Preaching to the choir and not reaching the sinner mpries@... | 10/29/07
Right on the dot KeeBored | 10/29/07
RE: 10 signs that you aren't cut out to be a developer alaniane@... | 10/29/07
Hobby vs. Professional Programming Justin James | 10/29/07
Build your own... Tell It Like I See It | 10/30/07
I should clarify alaniane@... | 10/30/07
Another good point ByteBin | 10/30/07
VS & databases Justin James | 10/30/07
Me too Tony Hopkinson | 10/31/07
The problem with advanced IDEs/code generation tools KeeBored | 10/30/07
The same here alaniane@... | 10/30/07
RE: 10 signs that you aren't cut out to be a developer rgsemail@... | 10/30/07
LOL Justin James | 10/30/07
Technospeak (or not) Tell It Like I See It | 10/31/07
College retro77@... | 11/01/07
And it's corrolary Tony Hopkinson | 11/02/07
RE: 10 signs that you aren't cut out to be a developer john3347@... | 07/27/09
RE: 10 signs that you aren't cut out to be a developer dbrown6@... | 07/28/09
RE: 10 signs that you aren't cut out to be a developer Noonelse | 08/25/09

What do you think?

White Papers, Webcasts, and Downloads

Recent Entries

TR on Twitter

Archives

TechRepublic Blogs



500 Things Every Technology Professional Needs to Know
Did you know Microsoft's RegClean does not work with XP but you can use shareware to clean your registry? Did you know most wireless access points don't have encryption enabled by default? Did you know there are 500 tidbits of information contained in TechRepublic's 500 Things Every Technology Professional Needs to Know that will help you become a successful IT professional.
Buy Now
IT Help Desk Survival Guide, Third Edition
TechRepublic's IT Help Desk Survival Guide, Third Edition provides tools and recommendations to help you better manage help desk services, improve end-user support, troubleshoot frustrating hardware issues, identify quick fixes to vexing Windows problems, and help users make the most of Microsoft Office 2003.
Buy Now

SmartPlanet

Click Here