| Programming really isn't such a bad job. Nor is it | | | | things. Pick an area of programming and learn all you |
| always such a walk in the park. After over a decade | | | | can about it. |
| in the business, I'm spilling the beans, so to speak, on | | | | Second, have some online samples of your work |
| the programming world. You won't find anything | | | | when you go for job interviews. Even if you don't |
| revolutionary here. What you will find is experience | | | | look at the examples during the interview, the |
| and some basic advice for those of you thinking | | | | prospective employer can check them out later and |
| about a career in programming. | | | | see what kind of work you do. Even if you don't |
| Programming is a job like any other, but there are | | | | write web sites or applications, you should at least |
| some perks to it. Typically, you'll get a desk, | | | | have screenshots and explanations of your samples. |
| computer, a decent chair, and even some air | | | | This is especially helpful when you are just breaking |
| conditioning. Right off the bat, that sounds like a | | | | into the business. If you don't have actual work |
| comfortable work environment. To be honest, it's not | | | | experience, a live portfolio of samples can make you |
| bad. You sit and you think and type. You draw | | | | shine. |
| flowcharts, analyze data, and play with a database. | | | | Finally, I would advise you to seek out employment |
| All in all, it's really not bad. Basically, you will get paid | | | | with smaller companies. Sure, you might not get paid |
| for three things: Thinking, typing, and solving | | | | as much or get great benefits, but there can be |
| problems. | | | | some perks to make up for that. In a smaller |
| Now for the rough part. This is something that many | | | | company, there are typically fewer rules. There aren't |
| programmers have to learn to deal with early in their | | | | any large committees meeting to determine how you |
| career. Some are fine with this circumstance, but | | | | should spend your day. You should work, yes, but |
| others are not. Many large corporations severely | | | | you might be able to do it how you want, instead of |
| restrict your computing freedom, and they do so | | | | how some committee wants you to do it. Going right |
| with antiquated systems. Sure, you'll have a great | | | | along with that, you might get some creative license |
| desktop computer, but you may find yourself | | | | in your projects. If you don't have a group of |
| interfacing with mainframe systems as old as you | | | | non-programmers telling you how to program, you |
| are. The company has to get all their money's worth | | | | can cut loose a little and create some really great |
| out of that system before upgrading, after all. Don't | | | | software. |
| be surprised if you run into a severe lack of | | | | Don't let the job market scare you. Right now, at the |
| creativity, corporate red tape, and dull-looking | | | | time of this writing, tech jobs are a bit scarce, and |
| cubicles. | | | | most of them are underpaid. Though that's no reason |
| If you are looking for a career in programming, I | | | | to pursue something else if what you really love is |
| have some basic advice for you. First of all, specialize | | | | programming. Programming can be a nice job if you |
| in something. I have found from experience that it's | | | | take your time to specialize and find a place where |
| harder to find a job if you have some skill in a lot of | | | | you fit. |
| things, than if you have great skill in one or two | | | | |