Measuring progress...
-
I'm in my 60s and I'm still programming and learning new stuff every day. Once I no longer find that interesting I shall stop!
-
-
-
I'm in my 60s and I'm still programming and learning new stuff every day. Once I no longer find that interesting I shall stop!
Somewhat the same here ... in my 60's, but learning new things about once a week. The rate has slowed as my employer is doing away with custom code. :(
-
In my experience a lot of people get too old to want to learn though ;)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Age has nothing to do with it. I know a lot of younger people who don't want to learn.
-
Damn kids!!!, get off my lawn
-
Damn kids!!!, get off my lawn
-
kmoorevs wrote:
My resources were mostly 1000+ page books
1000+ pages :omg: I got a few books in my early days, mostly like 300 to 400 pages, but nowadays I just read the docs of whatever I'm trying to learn.
kmoorevs wrote:
the MSDN CDs that came every quarter
I remember those, my dad always got them.
kmoorevs wrote:
I hardly ever bookmark anything anymore since most things are available via Google in mere seconds
Me neither for the same reason.
kmoorevs wrote:
The application that I started working on back in '99 is still going strong
Did you manage to keep the used technologies up-to-date? I've always found that to be the hardest part of programming... If you can't, working on such an old application could be a nightmare :omg: In my experience there's never time or money to upgrade or replace outdated technologies :sigh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
Did you manage to keep the used technologies up-to-date?
Good question. The answer is no...well sort of...it's a work in progress but will take a considerable amount of 'slack' time which there never seems to be enough of. I figure I've got another 5 years before MS stops including the VB6 runtimes and another few years before my customers migrate to that future OS. There's still time! :) I keep waiting to be able to afford a junior developer to pawn it off on. :laugh:
Sander Rossel wrote:
If you can't, working on such an old application could be a nightmare :OMG:
Actually, it's not bad at all...everything still works fine under Win10. It does get aggravating that the scroll wheel doesn't work there though and intellisense is not as intelligent.
"Go forth into the source" - Neal Morse
-
Yes, how many of us remember programming on and for those old mainframes?
-
Sander Rossel wrote:
Did you manage to keep the used technologies up-to-date?
Good question. The answer is no...well sort of...it's a work in progress but will take a considerable amount of 'slack' time which there never seems to be enough of. I figure I've got another 5 years before MS stops including the VB6 runtimes and another few years before my customers migrate to that future OS. There's still time! :) I keep waiting to be able to afford a junior developer to pawn it off on. :laugh:
Sander Rossel wrote:
If you can't, working on such an old application could be a nightmare :OMG:
Actually, it's not bad at all...everything still works fine under Win10. It does get aggravating that the scroll wheel doesn't work there though and intellisense is not as intelligent.
"Go forth into the source" - Neal Morse
kmoorevs wrote:
the VB6 runtimes
kmoorevs wrote:
it's not bad at all
Sounds like a bad case of the Stockholm Syndrome :wtf: :omg:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
