Slashdot Mirror
Programming Until Retirement?
DataDragon asks: "Here's the situation- I'm a now 30something computer programmer in Silicon Valley working for one of the local billion+ dollar tech companies. I'm unhappy with my present job, but am thankful that I've got one. Although I pride myself on having written over a million lines of code in my career, with nearly 15 commercial software products under my belt (8 of them were my own concepts from start-to-finish). I've had carpal tunnel for 6 years now, my skillset looks like it came from a 3 year old magazine, and I didn't make good on stock options. Since settling down in a quiet place somewhere and having a family sounds like a great idea to myself and my bride-to-be, I was wondering: instead of all the buzz I always get like Google's 'Do you <insert technology task> in your sleep?' job opportunities I've read about, are there any employers that would rather have a person who: wants to put in an honest day's work; get to know the job and the people well; and a desire to ultimately be a mentor for the company processes, instead of a here-today-gone-tomorrow programmer, who is interested in actually working there until retirement age?"
If you like programming, keep doing it as long as you can. If you don't like programming, stop immediately and do something you like. This applies to any field. On your deathbed you are not going to be worried about stock options, you are going to wonder if you wasted your life or not.
As people grow wiser and more experienced inside a company, they tend to move upwards towards mentoring/management-like activities.
Probably because their experience with coding makes them more suitable for taking decisions regarding project lead and also more suitable for giving answers to questions (in order to avoid repeating the same mistakes over and over again).
I've noticed that most companies do this - use their internal pool of experienced programmers in order to push them into mentoring/management positions, instead of throwing the management openings at the public and accepting CVs for it.
On one side, it's a good practice, because only those with previous experience inside the company will have access to those places, and by the time they get there they should know the process inside out. On the other hand, not throwing those positions towards the public makes them lose a full range of potential employees.
I'll back GreyWolf on that one. I've been programming for a while and had carpal tunnel. I switched and about a month later no longer had any pain :) Takes about 3 days to switch if you use it alot.
Also if you change the keys around while your learning it makes it alot easier.
The good: My company values its employees, deathmarches are rare, there is no danger that my work will be outsourced to India or Russia, salary and benefits are fantastic, and the work can be technically challenging.
The bad: The work isn't always technically challenging, you have to play The Game (but then, where don't you?), and eventually you will reach a point where you must take on some management responsibilities. However, if you work it correctly, you can rise as a technical lead, software architect, or some other position which is mostly technical with only a dash of paper-shuffling required.
I used to be a game developer. The work was incredibly fun, but the hours were backbreaking and the paychecks were irregular, if they came at all. As a mid-30s programmer with a wife, two kids, a mortgage and a car payment to worry about, I am willing to take some less exciting work in exchange for a company that treats me like a human being, pays me every two weeks without fail, and will gladly employ me until retirement if I so choose.
The federal government works on amazingly diverse and exciting software development projects, and they are looking for people EXACTLY like you. You can make a lot more than normal GS-payscale people, and get to work on incredibly interesting and unique projects. I'm sure that Military and intelligence agencies do some REALLY neat stuff, and you could be a part of it. You also get a real feeling of serving your country. The benefits are REALLY good, and if you plan right, you can make out quite well in retirement.
People who think they know everything really piss off those of us that actually do.
Starting your own business sounds great for someone that has never started their own business... However starting your own business is a pretty big gamble... Sure people succeed in creating their own businesses, but look at the statistics...
Most entrepreneurs fair starting at least 3 times before starting a successful business. A new business also costs money. It is typically recommended that you have enough money to support the business completely for the first 6 months without making a dime, and again there is no guarentee of success.
I mention it because it seems that people are flippently responding to start a business... It's a long hard road to start a business.
Furthermore, look at his requirements as I see them at least.
Work 9-5 programming
Steady work/job security
Working your own business, programming becomes the least of your skills. For example off the top of my head here are some of the requirements you need to run your own business.
Contract law - Always nice to know what your are agreeing to when you start a job.
Financing - Most people cannot afford to start their own businesses without outside help.. At the least you need to borrow from friends and family (something I actually recommend against since if the business fails your depleting their nestegg as well as yours) to borrowing from banks.
Business Management - Always good and probably the skill I recognised as the most needed during my own attempts to run a small business. You need to know the basics of business how to incorporate, how to manage employee's, how to determine what to charge...
Need to work more than 40 hours a week, small business owners in general tend to work a lot more than 40 hours a week, especially when they are first trying to get the company off the ground... This may very with proper financing, but still you'll likely end up working for more than 40 a week.
And though not really a knowledge requirement as a small business you must constantly seek work. Try to get customers paying a service fee so that you have regular income from month to month rather than requiring new contracts as each finishes...
These requirements are for a computer oriented business, if he were to go into another type of business he would have to learn about that type of business...
So lets review his requirements...
40 hours week --- Nope note likely
programming --- Not likely, running the business will take a majority of his time
Steady work --- Not likely, small business has to constantly seek work and anytime there is a fluctuation in the economy you may face a slowdown in work.
Job Security --- See steady work...
So as I see it, starting his own business requires none of his requirements.
/* TODO: Spawn child process, interest child in technology, have child write a new sig */