|
Sometimes, I think I've been doing this for too long - since early eighties - but then I look back and see how far we have moved.
Not just in hardware (though that is an enormous improvement on what we had when I started), or just languages (ditto), or tools (ditto with HUGE knobs on), but mostly in technique, and focus. Then it was "heads down, concentrate on the task in hand". Now, it is much, much more planning for the future, and trying to design re-use into modules from day one. This actually produces better results, even when we never reuse the code.
I may have been in the same industry for a long time, but it isn't the industry it was when I started, I'm glad to say. It's changed, and so have I.
Now, the "hobby" element is nearly eliminated from the workplace, and a good degree of professionalism is coming in to replace it. No bad thing, that.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
I wrote first computer code in 1980, but took software development as a profession over a decade later. Many professions involve writing computer code to some extent.
Best,
Jun
|
|
|
|
|
... Now that I have your attention, since 1998
|
|
|
|
|
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.
There is no reason why computing should be a young man's occupation because it relatively easy and inexpensive to acquire the latest H/W and S/W to keep up with the latest technology. I believe that it is every professional developers obligation to keep up to date. Once you've learned some of the basics such as how hardware works, operating systems, and compilers, it becomes easy to see new things in a context that you already understand.
|
|
|
|
|
There is no reason why computing should be a young man's occupation
true..
|
|
|
|
|
You are the best example for young man.  
<b>Today is a gift, that's why we call it present</b>
|
|
|
|
|
Absolutely agree. It worries me sometimes today to see young hotshot degree-holding developers who appear to have no real understanding of what is actually going on underneath what they are doing, i.e. at the lower levels. I know there's an argument that that is not necessary, but it's one that I don't subscribe to. Worse, these "young lions" are usually paid a heap more than me 
|
|
|
|
|
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!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
