Not Just Any Old Geek
Another old geezer here (43!); had a good run in my twenties and wound up in technical management a few years ago.<p>A couple of tips:<p>- The &quot;hands on&quot; technical skills that launched your career have capped (top salary) and declining value<p>- If you take time to learn &#x2F; think about how the underlying technology works (vs. just cut &#x2F; paste &#x2F; edit code), you can  master related new technologies faster than the average bear.<p>- It is also worth noting that technical challenges tend to repeat every couple of generations; the software developer community is operating within the same set of fundamental constraints (coder time, CPU speed, network, data, etc.), the main thing that changes is which constraint matters. And they repeat: at some point, CPU will be the constraint again and all ninja coder tricks of my twenties will matter again.<p>- Architecture, process design, and people herding skills only grow with time; 80% of my value as a manager consists of making unnecessary work go away (without drama). I am much better at using these skills at 42 than I was at 24.<p>- If you ever see an opportunity to build a side project that could turn into a business, take it. Even if you don&#x27;t replace your income, this gives you additional control over the direction of your late career and skills you acquire. Note that I said side project and not startup; the intent to get more control over your direction without walking away from your day job and associated income &#x2F; benefits.