Is it worth becoming a programmer? [closed]

Question

I'm a first year student in CS and I absolutely love programming. Many people have told me it isn't so good once you start working due to bringing your work home (thinking about how to solve problems throughout the day), working many hours when the deadline is near, and so on. I've heard being a system administrator is a less stressful job, since you don't have to worry about it at home.

So my questions are (for experienced programmers):

• Is it worth becoming a programmer?

• Does your job satisfy you enough to overcome these problems?

Thanks in advance.

Answer 1

If you love programming, certainly. As in any field, there are better and worse jobs. But once you manage to get experience, and find a good workplace (which is absolutely possible IMHO), you will get to do what you love, and even get paid for it (and quite well, compared to the population average)!

I do think this is a priceless combination.

Answer 2

I'm a first year student in CS and I absolutely love programming.

break;

If you like what you're doing, keep doing it. If those things bother you, there is enough variety in the types of things you can do after graduating, that you should be able to find a great fit.

Answer 3

60hr work weeks, taking work home, being on call 24-hours, etc... all that is not a factor of being a programmer. Thats comes from people unable to say 'no' to an employer. That happens in any industry if an employee lets their boss treat them like a floor mat.

The basic question is... do you like programming? Is it in your blood? Then be a programmer. Just dont be a floor mat.

Answer 4

It'll be what you make of it. Coming out of college I heard the rumors of 60 hour work weeks etc... I was lucky and my first job was a place that 40 hours was the norm and beyond that we were paid overtime. I took that philosophy with me ever since at every employer I have worked with no repercussions. Managers will try to convince you otherwise, as they say you are salaried. Even your co-workers will insist otherwise. But if your skills are good then you will win that argument.

At my current place of employment I am constantly hearing the developers next to me talk about how they are putting in extra time. They believe it is expected since they are salaried. Well...anytime I need to work beyond my 40 hours (other than an very rare single day here and there) I go to my boss and get my overtime approved with pay. It doesn't reflect negatively on me at all, I get top-performer reviews while my peers who work free overtime don't.

You'll only be abused and burned out if you let them abuse and burn you out.

Answer 5

No job is perfect or fun all the time. Yes programming can be frustrating, but believe me being the system admin and getting beeped at 3 am is pretty frustrating too. Being an accountant is frustrating, being an airline pilot is frustrating, being an artist is frustrating. All jobs have their bad points. You have to pick one where the good points outweigh the bad. You say you enjoy programming, then you are probably on the right track.

Answer 6

It depends. I think what you should ask instead it: do I like to be a programmer?

You see, in every field you choose, your are going to face a lot of challenges. If that's not for you, you're probably going to give up early or be in a really difficult situation.

It's really a stressing job and sometimes one may think it's not worth it, but if you love what you do you'll get through it.

Answer 7

These things you have heard were more true at the height of the .com boom. Short-term, a business can get a big push by throwing everything their employees have into their work. Long-term, people burn out or move on. Smart businesses have a strong emphasis on work-life balance. Keep in mind that some programmers really just love their job and want to take their work home and put in long hours, as well.

Rarely is coding an emergency, unless the business is not managed well. This isn't always true for a sysadmin. If the server goes down, the sysadmin need to get it up. If it is the production server, that's money being lost for your business. If it is an internal server, people can't get work done until it is fixed. Sysadmins rarely can work from home, but programmers usually can if they need to. On the teams I've worked on, it's not unusual for programmers with young children or bad commutes to WFH as much as once a week as needed.

If you love coding, keep doing it. Make sure you keep your skills up enough that you can always have your pick of jobs. When you interview, be choosy about work-life balance (if that matters to you at that point in your life) and don't be afraid to say, "I really don't like to routinely put in much more than 40 hours week after week. Once in a while, I'm happy to throw in everything I have for a weekend, but I don't want to spend all my evenings and weekends on work," if that's the case for you.

I find programming can actually be a very flexible, family-friendly job. I have 3 kids, two of whom were born less than a year after graduation from college (twins). I have great work-life balance, and even home-school my oldest children. I should mention that I am an SDET (I spend about 50% of my time on software development, 50% testing), but I think a programmer could do similarly well with their work-life balance. I do also think I want to someday do the "60 hours a week, just for fun" programming lifestyle, but that needs to wait until the other pieces of my life calm down.

Answer 8

Everybody brings home worries from their job, if you don't do that you just don't care about your job, it's just a question of learning the separate your personal life from your professional one. If a sys admin is at home and there's a problem he will likely have to go back to work and take a look at it, while a programmer rarely has to do this.

Now, I have some questions for you: Do you enjoy solving problems? Do you like logic challenges? Do you like building stuff?

If your answers to these question are yes you will enjoy being a programmer.

Answer 9

I am a programmer by job description, I love programming, but I have held jobs where I barely get to program. Mostly, I just updated fields in an online scrum software 'real-time' (sic), attended hour long status/kick-off/design/analysis meetings, read scrum stories, read horribly written code, refactored others' code (thereby creating more refactoring work for the next day,) read proprietary asinine specs and suffered, became frustrated and updated resume, etc., The only 'programming' I get to do sometimes is when I try to implement programs to solve the questions from stackexchange network...

Long story short, 1. every job can be joyful if you do it with passion. 2. it is not always about programming in a programmer's job

So, ask yourself, "am I passionate about programming?" If yes, become a programmer. If not, don't become one. It will help lot of passionate programmers from refactoring horrendous code.

Answer 10

Working in general doesn't feel as good as doing something just for fun.

Getting paid for it though feels very, very good indeed.

But you get all sorts of environments you can work in small businesses, large businesses, formal or casual, process-driven or agile, jack-of-all-trades or specialised, it's unlikely that there isn't a single environment out there that doesn't suit you.

Most people who are unhappy doing this job are simply working in the wrong subtype of programming. Or they could just love moaning. :)

Answer 11

The difference between a programmer and a sysadmin, in terms of how your work "flows," is this: Programmers have projects, sysadmins have jobs.

What I mean by that is a sysadmin has a particular set of jobs (made up of tasks) that they do each day. Mostly they are independent jobs, and when they are done, they are done.

Programming projects tend to be drawn out over weeks, months, sometimes years. This means you have to be able to understand what you did a long time ago to figure out how to move forward. This can be stressful. However, it can also be satisfying.

If you like this sort of long-term strategy, programming is probably a better career. If you prefer to get things done and be done with them. A sysadmin is better.

Of course, there are many other differences. But related to the point of "taking your work home" Both do that, but in a very different way.

Answer 12

Many people have told me it isn't so good once you start working due to bringing your work home (thinking about how to solve problems throughout the day), working many hours when the deadline is near, and so on.

This is all true.

But as others have said: If you like to program, then it's very nice to get paid for doing something that you like to do. Most people on Planet Earth do not have such a luxury.

However, I'd like to add another point.

Programmer compensation, relative to other occupations, is generally commensurate with talent and skill.

• We've all heard people grouse that they are not paid what they are worth.
• Well generally speaking, over the long haul, programmers are paid what they are worth.
• When programmers notice that, in the moment, at a particular company, they are not paid what they are worth, they leave and find another employer who will pay them what they are worth.
• People in other occupations do not have such a luxury.
• In fact, many people in other occupations are vulnerable to the sea change that programmers (through no fault of their own) are powering with increasing automation.
• As I see it, I'd rather be employed in a field that's in demand rather than in an field that's vulnerable to increasing automation.

Answer 13

Even if you don't like it, it is worth a lot, because most people:

• Don't have the scientific curiosity required

• Fear things they find cryptic

• Are frightened to turn into a geek

• Are also frightened to "not be good enough"

To me, among all applied sciences (unlike maths which aren't directly applied), CS is the one I prefer, simply because:

• You can practice it just by having a computer, even a crappy one

• You can experiment other sciences, because a computer is a mathematical tool

• Every simple task a human can do, can be mimetized with a computer.

• It is the one that best represents the way "intelligence" works at a very low level.

For all those reasons, working in programming is at the same time infinitely interesting and rewarding, because the service you give, hardly no other computer-less person can match with quality and speed.

On the other hand, CS is very young, and I think it still has a lot of problems that will need to be solved in the future.

One day I heard a teacher said "computer science is evil because it solves problems that it creates", like cell phones for example. I will always think those claims are the most negative I ever heard about innovation.

The true thing about CS, is that we could live a lot better by things we can still invent, but have no idea how it could really make our life better. That's where you understand what a true invention is.

Answer 14

• sure it is
• if theese are problems for you, yes. for me they aren't (compared to a usual job where i always have to be nice to everyone, smile and do something that is way below my capabilities and nothing interesting at all just to have my wages at the end of the month...)

Answer 15

If you think programming might not be what you want to do, a good idea would be to consider what other options there are for you. Is there anything else that really interests you that could potentially work as a career after you graduate.

Having to take work home is a downside to a lot of different jobs, but there are also programming positions that are much more likely to only involve your 9-5 hours if you're willing to take less money (government is one example).

I think if you really enjoy doing it, then you shouldn't reject that as a career unless you find something that works better.

Answer 16

System admins are the guys that are always on call. If you want to have a quiet home life programmer is the best in the tech field. Granted this is a profession where you will spend time working on this stuff at home but as long as you find a good company to work for it wont be excessive. If you go to work at a startup the hours may be insane but you'll be working on cool stuff, if you get a job at a big corporation the hours are likely to be better but you'll most likely find yourself working on tech that is legacy and even your greenfield projects will most likely run on software that is 2-3 versions behind. The trick is to find a company right in the middle, small enough that you get your hands dirty with some bleeding edge stuff and big enough that there is redundancy in your role so you're not the only programmer.

Answer 17

System Administrators, especially junior ones are required to be on call all the time. If you like getting calls in the middle of the night to remotely log in to machines and bounce servers, more power to you. Developers much less so unless they are front line support, and still some SA is the one calling them after not being able to solve the problem.

Developers have to continuously study their craft, learn new frameworks, languages, techniques and tools. Much like doctors and lawyers have to continuously learn. System Administrators not so much. Most server environments like Enterprise Linux ( pick any distro ) or any other Unix, don't change for YEARS!

Answer 18

Well, I have this case. How would you feel if you worked at a place like this:

• Bad management would lead to every single project to be tagged as urgent. No strategic plan, no certainty about anything, just a sense of urgency and a matter of crazy politics influencing the corporate decisions. Therefore the boss would call the whole office just to scream and complain that we were not working hard and fast enough to meet the so-short deadlines we had, but never to work on a plan.

• The president of the company would be so hormonal that he would ask for results in less time with less resources thus threatening employees of being fired.

• A programmer working on up to three projects at a time.

• A bunch of users asking for results all the time.

• A boss who would not defend his group against external annoyances and would happily accept whatever requirement that came from management or other offices even though the whole software development group would be too busy to do anything else.

• Computer programmers also doing sys admin due to "lack" of resources. When something went down, the boss would immediately scream at one of the programmers so that things would go up again. When projects were lagged behind just because of us doing sys admin instead of working on the projects, the boss would, with no excuses, ask for results from those projects, thus leading us to work extra-hours for no pay.

• The boss would threat an employee of being subject to legal punishment in case he/she would oppose to sign a document that doesn't concern him/her directly.

• Employees were asked to pay a fee so that their short-term contracts would be renewed. No pay means no "supporting" the group thus no renewal.

• A secretary that would take the boss' place in screaming at everybody what they should do.

• A general feeling of uncertainty about the implementation of the developed products due to constant changes in phylosophy.

The "good" things:

• Medical insurance.
• Good pay ($ 1,000 month is considered good).
• You may get a steady position if they decide.

I resigned some months ago from that job due to the huge risks I was about to face, although I had some financial benefits due to my years of work there, but I see many of my older friends to bear with that just because they need money to support their families. However, some people tell me I didn't make a good decision since, at least in my country, it's becoming more and more difficult to find a job.

However, I feel that I have been affected psychologically to the point that even at this point I still feel frustrated and dissapointed and I'm considering pursuing another career.

Tell me: IS IT THE NORM TO HAVE WORK ENVIRONMENTS LIKE THIS???

Answer 19

Hey! The right question is "Am i Worth being a Programmer". Because programmer is not just a job.

If Math & Logic fascinates & you like taking up those challenges to solve, then you are worth of being a programmer.

How long you want to be a consumer or a parasite of technology. Be a GOD, i mean Generator Organizer & Destroyer, of technology.

Speaking form the Industry point of you, be proud to be the Crux of a company.

Finally, i wanna say that don't mess up you passion by small souled people's thoughts & words.

I am Proud to be a programmer, more over i love my Job for giving me challenges to prove myself.