Programming is not a long term career
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
My new company is relatively young and their a few over 40's [I am one of them] but I still do some coding, just not that much. In my previous job, the demographics were very different and in my department of around 50 there were 10 over 40's and some even over 50 who were still coding. But remember that as you progress through your career, your priorities change. I can produce far more effective results by instructing a team of 5 coders then by cutting it all myself. Look at PO'H, he's a pretty damned hot code monkey, but AFAIK he rarely writes anything himself anymore. Again his priorities have changed.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I think it depends where you are, when I worked at an AFB there were a lot of older programmers... you know, the ones that look like serial killers... ;P :laugh:
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I've been doing it since 1980, and actually being paid to do it since 1982. I imagine I'll be doing this until I'm 70 or so. My dad had been an electrician for about 60 years, and only recently had to quit wehen he had a stroke last September. Most programmers are mmoved into management positions between 35 and 40, and that's why you don't see that many old programmers. Me? I hate people, so management isn't exactly the right career path for me. For the most part, people leave me alone and let me write code, and I'm fine with that.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I'm like you and have been programming many years. I started my own company to avoid being promoted out of the dev part of the job. Now I do everything and am having a ball. :cool:
It’s not because things are difficult that we do not dare, it’s because we do not dare that things are difficult. ~Seneca
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I think you can say that about any career path, you know the Peter Principle: where people tended to get promoted up to their level of incompetence. :laugh: I don't know, it seems that there are a number of "old" programmers here at CP. Where I work it seems that the age range is actually quite spread out. Yes the older programmers do get the project lead positions or move to being a manager but are still involved with coding. At least the ones that keep their skill set up to date.
It was broke, so I fixed it.
-
I've been doing it since 1980, and actually being paid to do it since 1982. I imagine I'll be doing this until I'm 70 or so. My dad had been an electrician for about 60 years, and only recently had to quit wehen he had a stroke last September. Most programmers are mmoved into management positions between 35 and 40, and that's why you don't see that many old programmers. Me? I hate people, so management isn't exactly the right career path for me. For the most part, people leave me alone and let me write code, and I'm fine with that.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997John Simmons / outlaw programmer wrote:
I hate people, so management isn't exactly the right career path for me.
Oh John, I can just see you as a manager. You'd hire the BOFH and destroy the bean counters. :-D
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
I think it depends where you are, when I worked at an AFB there were a lot of older programmers... you know, the ones that look like serial killers... ;P :laugh:
Albert Holguin wrote:
older programmers... you know, the ones that look like serial killers...
Hey I resemble that remark! :) Seriously I'm 46 and I have no aspirations to management so I guess I'm stuck as the greybeard programmer! My boss hates that the only thing I put on my IDP (Individual Development Plan) is Mo' Money!! :-D
The environment that nurtures creative programmers kills management and marketing types - and vice versa. - Orson Scott Card
-
Albert Holguin wrote:
older programmers... you know, the ones that look like serial killers...
Hey I resemble that remark! :) Seriously I'm 46 and I have no aspirations to management so I guess I'm stuck as the greybeard programmer! My boss hates that the only thing I put on my IDP (Individual Development Plan) is Mo' Money!! :-D
The environment that nurtures creative programmers kills management and marketing types - and vice versa. - Orson Scott Card
Joe Simes wrote:
the only thing I put on my IDP (Individual Development Plan) is Mo' Money!!
Max respect!
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
I think you can say that about any career path, you know the Peter Principle: where people tended to get promoted up to their level of incompetence. :laugh: I don't know, it seems that there are a number of "old" programmers here at CP. Where I work it seems that the age range is actually quite spread out. Yes the older programmers do get the project lead positions or move to being a manager but are still involved with coding. At least the ones that keep their skill set up to date.
It was broke, so I fixed it.
We are also the ones they keep around to maintain (really) old code ... since we are the only ones who have experience with the languages and tools. Cobol, Fortran, Pascal or 8086 assembly anyone? ;)
Steve _________________ I C(++) therefore I am
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
-
We are also the ones they keep around to maintain (really) old code ... since we are the only ones who have experience with the languages and tools. Cobol, Fortran, Pascal or 8086 assembly anyone? ;)
Steve _________________ I C(++) therefore I am
Steve Mayfield wrote:
Cobol, Fortran, Pascal or 8086 assembly anyone?
ow, my head hurts... I still write assembly for Freescale HC08s. I guess that means I'm old :sigh:
It was broke, so I fixed it.
-
We are also the ones they keep around to maintain (really) old code ... since we are the only ones who have experience with the languages and tools. Cobol, Fortran, Pascal or 8086 assembly anyone? ;)
Steve _________________ I C(++) therefore I am
I hope I've forgotten my COBOL; it must be nearly 20 years since I cut any.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I think this might be more a function of history. I mean just how many programming jobs were there 30 years ago compared to today? Yes, there were programming jobs in the 80s, but there are *so many more* programming jobs today that the personnel ratio is diluted. Ergo you would *expect* there to only be 1 50+ year old programmer to every 6 20 year old programmers because there were only 1/6th the number of programming jobs back when the 50 year olds started their careers (note these number I use were very scientifically pulled from my a*se). Also note that -- completely anecdotally -- my team of 3 developers includes 1 40+ year old and 2 35+ year olds.
-
I think this might be more a function of history. I mean just how many programming jobs were there 30 years ago compared to today? Yes, there were programming jobs in the 80s, but there are *so many more* programming jobs today that the personnel ratio is diluted. Ergo you would *expect* there to only be 1 50+ year old programmer to every 6 20 year old programmers because there were only 1/6th the number of programming jobs back when the 50 year olds started their careers (note these number I use were very scientifically pulled from my a*se). Also note that -- completely anecdotally -- my team of 3 developers includes 1 40+ year old and 2 35+ year olds.
Actually... 3 35+ yr olds, unless the 1 40+ is already counted in your set of 35+
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
A lot of older programmers (50s, 60s) are stuck in business oriented domain ( banking, insurances ) and work on older systems; or are working for large consulting firms that specialize in high level business application. My experience is that most people I know in programming are in their early 40's and going strong.
Watched code never compiles.
-
I love programming but I think the context is important. If I had to choose between writing javascript for the next 30 years or managing others to do that, I'm choosing management.
I would make up a new option: Write a program to manage the javascript.
-
I hope I've forgotten my COBOL; it must be nearly 20 years since I cut any.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I'm below 50 and coding like my fingers are on fire, I can run circles around newbies and it's all down to experience. The more experience you gain the better and easier the job becomes. I have an intern in my office at the moment (he's 20), he can't believe I have solutions for every problem he encounters. I doubt I'll be hanging my coding keyboard up for a long time, if fact I'll still be coding until I retire. The only problem I see for the future is that the internet has allowed it to become easier to program (sites like CP make it easy), the wages will drop to a point where it won't be worth programming for a living unless you have a niche technology. I wouldn't recommend programming for a living if you're young, things are changing.
www.software-kinetics.co.uk Wear a hard hat it's under construction
-
I've been doing it since 1980, and actually being paid to do it since 1982. I imagine I'll be doing this until I'm 70 or so. My dad had been an electrician for about 60 years, and only recently had to quit wehen he had a stroke last September. Most programmers are mmoved into management positions between 35 and 40, and that's why you don't see that many old programmers. Me? I hate people, so management isn't exactly the right career path for me. For the most part, people leave me alone and let me write code, and I'm fine with that.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Same here John, I hate management, somehow I've managed to avoid it. Everyday I actually enjoy coming in to work.
www.software-kinetics.co.uk Wear a hard hat it's under construction
-
To those of you who program for a living, look around. How many programmers do you see who are older than 30? Older than 35? Older than 40? It's my guess that, as you proceed through the increasing ages, you will find fewer and fewer hands-on programmers. So what's that mean to younger programmers, say, in their twenties? I believe that it means that programming is not a long term career path. As programmers become older, they fall prey to the niceties of management (carpets, big desk, a door that closes, etc.). And as a result, fewer and fewer programmers have gray hair. Maybe a lot of managers do but few programmers do. I'm a lucky one. I continue to program. And I'm old! But I think I bring a far ranging experience to the table. I am cautioning young programmers to beware. Although you may think it is, programming is not a long term career.
I don't think the future will confirm what you are saying. Programmers have traditionally been young because older people simply didn't have access to computers until very late in life. My father and mother didn't have computers as a child, didn't have the option of choosing Computer Science as a major when they started college, and so on. As computers become a more commonplace technology, a broader spectrum of age groups are becoming familiar with them. Today, there are plenty of 40-year-olds who had computers as a child, and as a result there are plenty of 40-year-old programmers (or, at least, there are more than there were in 1985). The other thing to consider is that demand for programmers is still very strong, and salaries are still high. It's easy to make blanket statements about programming being a young man's game, but I have yet to actually find this supposed army of young, skilled programmers that's out there. In fact, there are some real trends that point to programming becoming an old man's game. The number of CS graduates is stagnant, and these graduates tend more and more to be educated in easier technologies like Java (which is a great language, but much more abstract / less intellectually demanding than the languages in which I was educated). The stereotypical hacker of yore - who lives on Jolt cola and can hand-assemble code for three or four different CPU families - is pushing 60 now; do you know any 20- or 30-year-olds like that? So far as I can tell, society simply does not produce very many of that sort of person (and rumors of their obsolescence are exaggerated).