Hey, thanks ruling out the 60s as too old even to consider. :)
I think anyone who is a seat-filler has a problem. But if one codes for fun, if one sees new technology and just DLs a tutorial and starts using it, if one is always thinking about how ones code can be tighter, such that every time one looks at ones code one rewrites it, one will be OK.
No need to stop coding to make money. Top coders do fine, and then one gets to code.
I am consulting for a company where I gave up a top spot so I would have more time to work on my startup: http://tiltontec.com/
I am sixty-two, have been coding head down on hard problems since 1978, on the Apple II.
I think anyone who is a seat-filler has a problem. But if one codes for fun, if one sees new technology and just DLs a tutorial and starts using it, if one is always thinking about how ones code can be tighter, such that every time one looks at ones code one rewrites it, one will be OK.
No need to stop coding to make money. Top coders do fine, and then one gets to code.
I am consulting for a company where I gave up a top spot so I would have more time to work on my startup: http://tiltontec.com/
I am sixty-two, have been coding head down on hard problems since 1978, on the Apple II.
Good news, grasshopper: it never gets old.
Now if you'll excuse me, it's time for my nap.