|
I agree - and it is difficult to see where this is going to lead. You know and I know that the lowest levels haven't changed significantly, but that layer after layer has been built on top of them.
Should a new paradigm evolve - organic computing say - how will the latest generation cope with replacing the creaking tower to reach the levels they are at now? As the old generation are squeezed out of the industry (by design, by death, or by default) can the "young blood" fill in the gaps? Not too likely on current showing. 
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
baw wrote: The first computer I programmed (in 1959) was a Stantec Zebra, a paper tape based machine.
The last computer I programmed (in 2011) is an Apple iPad for which I am developing an app to display Sharepoint data.
|
|
|
|
|
|
I started developing (writing my first C code and never stopped then) in 1999.
I professionally started developing software and working with Professional companies in 2005.
With 5+ experience, i see many more people like me, with this survey results.
Current survey results comparison to 7 years back results:
- more people do not work as developer now
- there are more people who have just entered in coding now (w.r.t. compare count then)
- there are more senior developers and developers (not beginners) now
- very less developers now, who have very high experience
|
|
|
|
|
I've been developing professionally since....damn....1981.
Anton...
Anton R. Bruce Sr.
|
|
|
|
|
And hiding behind the wood pile since 2005? You do realise that was your first post since you joined? Congratulations! We need more mature, professional, developers here sometimes... 
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
Yeah I started programming in 2004 & now 2011 & If I survive the 2012 doomsday, I'll do continue till 2025.
|
|
|
|
|
Huge mainframe at UNC Chapel Hill and a string of 'minicomputers' after that.
Started programming desktop computers in 1970 - Olivetti, Wang, then in 1974 dove into the HP-9830, which was great because of its graphics abilities and the powerful (at the time) Rocky Mountain Basic. It wasn't until YEARS later that Apple came out with its first offering.
Now? C++, C#, ASP.NET, Javascript, SQL etc etc. I'm hesitant to count SQL among my languages being as it's neither structured nor a language
Steve Lackey, Sarasota, FL
|
|
|
|
|
My God!
Look at nearly 50 Years!
Congrats, let us know when you get there, we'll throw a party 
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
CCC League Table Link
CCC Link[ ^]
|
|
|
|
|
its not possible for me to join the party physically, i´ll have a good single malt tonight
I cannot remember: What did I before google?
|
|
|
|
|
Thats amazing, i see my self going on same path to develop and code in coming year
All the Best and hope it goes on
|
|
|
|
|
Truely awsome, more years than I've bee alive (but not by much).
Keep it up!
Ken
|
|
|
|
|
You seem to have lived an almost parallel life to mine, although a little longer in the development sphere (see post below). I was thinking of aiming for 50 years myself at one stage, but now maybe not. Chances are I will still be developing for that long, but not professionally. Basically, if a device is programmable in any way, I've always felt the need to figure out how to drive it. I think it's a fundamental personality flaw or something
|
|
|
|
|
Gawiz wrote: SQL ... neither structured nor a language
It's a language for giving structure to your queries -- (Structured Query) Language, not Structured (Query Language).
It's just not a general purpose language.
|
|
|
|
|
It was really just sort of a linguistic joke 
|
|
|
|
|
Well, I've been professional now for about 17 years, and I'm 39 years old. Kids never have had it so easy if you ask me, starting with something like .NET. Try using the MIDL compiler, doing anything with COM, using special calling conventions to export stuff from a DLL, and heaven forbid 32-16 bit thunking. That's actually a rant and not the point I want to make.
IT has always been a young man's game because the skill is so new, and I've been concerned for a while what I'll do when I get into my late 40s, it's incredibly ageist, and I suspect getting employment however good you are or how well your CV reads is going to be difficult (or low paid). Most of the people I work with are quite a bit younger than me generally. That said, I do know people who look for those in at least their 30s, who have done some heavy duty stuff like C++ in their past before everything became Mickey Mouse and everyone jumped on-board.
Regards,
Rob Philpott.
|
|
|
|
|
I'm 41 and I know the pain you've had. Mine is a very long and winding path of discovery - one I still enjoy a great deal. Getting older might mean you find it harder to learn new technologies, but I think if the magic never dies then you just get better and better at learning. As for technologies like .NET, someone has to do the low level work (it could be you!) but I'm just glad things have moved on and I can focus more effort and time on giving my users what they want and need rather than fighting the machines, libraries and operating systems.
Don't worry, nobody lives forever.
|
|
|
|
|
In 20 years everything "we youngsters" did now with .NET will look painful too I bet!
|
|
|
|
|
I'm 62 years old and still working as a maintenance programmer. I started programming for a living in 1973 (yes - almost forty years ago). It's been a battle the past few years to convince people that I can still learn new things at my "advanced" age (that's real age discrimination). The other battle I've had to fight is the push to move me to management. I never wanted to manage. I always wanted to do maintenance programming and I am good at it.
I've been working in my current job for about fourteen years. Our applications were written in VB6 starting in about 1999 and one was converted to VB.NET about five years ago. I don't feel that I'm that out of date but I certainly don't feel like learning any new languages any more. A lot of what a programmer does is not tied into the language. It's transportable to new languages and new machines. I did a lot with C for several years and I don't feel uncomfortable working in C#.
I can't get over people complaining about COM and working with DLLs. Try maintaining a few million lines of assembly code developed over fifteen years that uses custom hardware that no one else in the world uses.
|
|
|
|
|
I hear you. I'm 52 and looking for a new job. I've been with my current company almost 8 years. I am a C/C++ heavy hitter (and have been for a long time). I've learned Python and Java in the last year. But I still can't convince interviewers that the gray hair/bald head doesn't mean the brain has hardened.
-- Martin Goff
mlgoff@commspeed.net
|
|
|
|
|
Same with me. I am 53 and just got a job after being out of work for almost 21 months, aside from a couple of contract jobs. I started back in high school in 1973 and left college to become a full time programmer in 1977.
I have written a multi-user/multi-tasking operating system, several language interpreters and compilers (one of which used a virtual machine I invented), debuggers, libraries, etc. Projects that could have been for a Masters or Doctoral thesis.
But since there was no call for those skills here I decided to go back to school to pick up new skills and to work on finally getting my degree. Now I have a job and I am going to school, which leaves me very little time for anything else. I figure picking up some new skills and a degree can't hurt for the future.
Many jobs out there seem to want certifications to "prove" you know something. All that proves is that at the time you knew how to answer questions on a test. At one place we had a guy with a doctorate in Computer Science that was worthless. Turns out all he knew how to do was copy code from somewhere and try to massage it so it sort of worked. If it didn't he had very little chance of fixing it. One time he wrote a sort routine inside out and backwards, guaranteeing that it took the maximum time to sort the data, which meant the communication link waiting for the data got dropped due to a timeout. We finally had to fire him.
But try and convince some HR person that past work is a better indicator than a piece of paper. Heck, they often don't understand what they are hiring for! just look at how they word (or misspell) the ad for the job sometime!
|
|
|
|
|
that's why I'm going back to school this fall too. Today, you need to paper to get the interview.
-- Martin Goff
mlgoff@commspeed.net
|
|
|
|
|
I've run into a few developers like that too. They are great at architecture and writing new code but some of them can't debug code at all. My job most of my career has been to follow behind developers and make their code work after they are done with it.
|
|
|
|
|
I am also 53 years old and while I have done a lot of job hopping in the past 8 years since the dot com bubble burst I have been generally able to find a new position within a month or two. It's pretty easy to blame our age for all of the troubles finding new positions. It could be a person's interviewing skills are not what they should be especially when they have been working at the same position for over a decade. It could also be that the person in question is as valuable in the market as they believe they are.
It is true that a kid coming out of school with a graduate degree may know nothing real-world coming into a company it has been my experience that they usually come on line very quickly and become real producers in a short time. You don't need a graduate degree to be sharp, but you need to be sharp to get a graduate degree; they don't just hand PhD degrees out as door prizes. Don't be so quick to discount his education or abilities, part of the reason why he didn't work out could be communication issues if he wasn't a native English speaker or your system might have been so dysfunctional that he couldn't work within it without assistance which he may not have received.
|
|
|
|
|
That was not the case here. He was no kid and he was writing new code. I was called in and pointed out the problem in his code. He then spent 2 weeks trying to "fix" it. He was finally taken off of it and the code was fixed and tested using my suggested method within an hour.
I am not saying everyone with a degree is like that, just that having a degree does not mean that you are killed and competent because you have it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
