Labor Market and Career Information

Programmer/Analyst/Administrator
Mark Duksta

	Introduction Do you know how a computer works? Do you understand how the Internet functions? If you were Mark Duksta, you would. Mark is a Programmer/Data Analyst/Network Administrator at a small software company in Austin. He does everything from writing code for software products that the company sells to making sure that all the office computers stay connected and compatible. He backs up the servers so that no data are lost if something catastrophic happens and he ensures that the office email functions properly. If he sounds like a one-man show, it's because he CAN do it all, though he has help. And he didn't even start working with computers until he was in his 30's! Mark's story is an inspirational one. He left a career that made him unhappy and got the education and training he needed to start anew in a field he loves. That change required sacrifice and patience, but he did it. And today he works in an area--information technology--that will have plenty of job openings for years to come. No job is guaranteed these days, but if you have the kind of skills Mark does and you share his willingness to keep learning, you'll never have trouble finding work!

	What exactly do you do? The company I work for is small, so I actually do a combination of three jobs. As a Computer Programmer, I create interfaces [what you see on a computer screen] to present data. As a Data Analyst, I talk to users in their own language and translate what they want into computer language/programming. I have a Business degree and that helps me understand business lingo. And as a Network Administrator, I maintain network equipment [the computers, servers, etc.], help users [e.g., my coworkers] and set policies and procedures for the system.

	Describe a typical day. Before I go home each night, I leave a note describing where I left off. When I get in each morning, I know where I am and can begin coding immediately. Throughout the day, I program and/or troubleshoot the problems users might have. Every day is different.

	What's the coolest part of your job? Getting to know and use all the latest technology. There's always something new. It's fun.

	What's your favorite part? I like creating something in a text medium [programming]. Once I get on a roll, I don't want to stop. Ten hours could pass and I wouldn't even notice. And I like the excitement of seeing the final results of my work.

	How do people react when they learn what you do? I live in Austin so people are used to meeting programmers. They usually say "That's cool." I get a lot of questions about problems with their computers or about how something works on the Internet. I enjoy the questions. The hardest part is to put it in terms that aren't too technical so that it stays interesting for them.

	Describe a funny or unusual incident that happened at work. The one that first comes to mind concerns a former coworker. She was not very computer-savvy but she could get by. One day, though, she was getting frustrated because she couldn't get her CD into the CD drive. It turns out that she was trying to stick it into the crack between the drives! I couldn't believe it. It was like one of those jokes where the person thinks the CD drive is a place to hold their coffee mugs.

	What's the part you like least about your job and how do you handle it? I dislike routine meetings. I think a meeting should have an agenda and a goal. I deal with it by making sure that the meetings I call have both.

	How did you become a programmer? It's really my second career. When I was in high school, computers weren't very common so I didn't think about being a programmer. I actually got a degree in drafting but I found that I made more money in my job as a grocery store manager. I worked as a manager for many years but became unhappy with it. It's a very demanding job. I'd been using a computer at work and I had a home computer that I really enjoyed playing on. Eventually I decided to study programming as a career. I went to school part-time at first and then finally full-time. Once I got my degree, I began my new career.

	What pleasantly surprised you about your job when you first started? The autonomy--you could solve problems in your own way within programming guidelines. In school, there was a "right" way to do things--the instructor's way. In my work today, though, I get to solve problems the best way I know how.

	What disappointed you? Having to do so much maintenance programming. Every job includes a little maintenance programming, which means updating code that others have written. I had to do so much at my first job, though, that I got my current employer so that I could do more original programming.

	How has your job changed over time? I've gotten promotions, increased pay, increased responsibilities. Because I have gained seniority (meaning I've worked here longer than most of the other programmers), I have some unofficial say-so in what goes on.

	What will people in your field be doing ten years from now? Programmers and analysts will have more automated tools--something that's happening already. Instead of writing lines of codes, we'll be able to insert whole chunks of it at once or condense it to one line. I think programmers will still be needed as long as people want customized software.

	What are some of the most important skills and abilities needed for this job? Logic, problem-solving, the ability to understand a problem and see a solution in way that the computer can achieve. I can visualize problems and solutions spatially, which helps. And I'm stubborn, which also helps. I think it's important to like what you do, too.

	How much of that is learned and how much has to be natural aptitude? I think you could learn it all without natural aptitude but those with an aptitude will think it's fun and be better at it than those without.

	What information do you need to keep up in your field and where do you get it? I have to keep up with emerging technologies and the new software that's available to solve old problems. I get the information by reading trade magazines, scanning the Internet, talking with other programmers, and attending conferences and training classes. In just the past few years I've learned at least two new languages and dozens of software programs.

	What advice do you have for people who want to enter this field? Get a Bachelor's degree. Although a four-year degree is not necessary, it's easier to get a job with one and you get better trained to talk with potential clients. Get a computer and find some tasks that excite you, that make you want to work on them. Create something. If you're interested in music, for example, catalog your CDs on your computer. You won't really learn to use your computer until you encounter problems and solve them.

	What do you wish someone had told you before you left high school that would've helped you with your career? Try to see where you want to be in 5-10 years and investigate ways to get there. If you don't, you may be too old later on. You can't decide to be a medical doctor when you're 40 years old, for example. I wish I'd planned ahead. Instead, I delayed getting into my career and settled for the best kind of career I could get at the time. I enjoy Programming, but I might have become an Engineer if I'd started earlier.

	Quick Facts
	The Job in Brief
	Title:	Programmer
	Description:	Create software, translate users' ideas into computer language and maintain network system and equipment.
	Education level required:	Associate's degree plus experience or Bachelor's degree Mark has: Bachelor's of Business Administration with a major in Management Information Systems
	Equipment used:	Computers, standard office equipment, cable tester, crimpers to make cables and hand tools (to take apart the computers).
	Workload steady or fluctuating:	It fluctuates. We're really busy when we get new data for our programs or when project deadlines approach.
	Dress code:	Casual. Programmers are generally laid back.
	Work environment:	Office with cubicles.

	Demands on Worker
	Works hours (time and duration):	40 hours or more, depending on the project. Most network administrators have to be on call on weekends and nights.
	Travel involved:	Score: 1 (to attend training sessions) (1=never; 5=very often)
	Average stress level:	Score: 2 (1=none; 5=a lot)
	Amount of teamwork needed:	Score: 3 (1=none; 5=a lot)
	Level of self-motivation required:	Score: 3 (1=none; 5=a lot)

	Labor Market Information
	Employment outlook:	Employment of programmers is expected to grow faster than the average for all occupations through 2008 (at least).
	Typical Texas salary:	$46,537 to $56,879 a year