Making sure that we would have a job when we get old

I’m a software engineer in mid-30s, what do I need to do to make sure that I have a job when I’m 50? I would like to stay in the technical career path.

Stephen Burns · Updated March 19, 2019 . Senior Software Developer

I’m 49¾. I’m just a developer and I do well enough getting developer positions.

Here’s a few observations based on my experience working in functional work-places:

1. Be able to code: It’s surprising how many developers can’t do this tolerably well in their chosen language.
2. Have expertise in something relatively current: By the time you’re 50 you should be good at something.
3. Know the why for the things you claim expertise in.
4. Be curious: Google the hell out of shit. I am naturally curious so I want to understand how stuff works. We all have a balance between wanting to understand how that library we’re using works versus just getting shit done by copying the strategy that Jimmy used for a similiar task. I favour the former which typically means I under-perform for a few weeks in new jobs. I still end up re-using Jimmy ‘s shit most of the time but I understand why I did it; occassionally I come up with a better way of solving the problem and that becomes the new template. (Future) colleagues appreciate people who know stuff. Trying to fix broken shit with little or no understanding is like trying to type with two fingers - it works but it’s time consuming.
5. Always be learning: Developers with depth of knowledge are hard to find. Developers with domain knowledge and depth are gold dust. Learn about the technology your company is using, the technology they could be using and, the domain they operate in. And keep an eye on what employers are looking for.
6. Be a giver: Take opportunities to help colleagues improve. We provide value to our colleagues as well as our companies. Our colleagues may remember the value we provided when they move on.
7. Take on responsibility: On rare occassions you may have to fight for it. Responsibility sits well on a resume.
8. Be a pessimistic optimist: Your code reflects that you expect the worst to happen and you question the hell out of shit when digging into requirements/design but your behaviour reflects optimism in getting shit done.
9. Maintain your health: The older you get the more this matters. From 40 onwards, unlimited sugar and fat in the form of work-supplied free biscuits, sweets and, fruits is tempting but not conducive to top-drawer coding. Responsible imbibing of caffeine and bananas is all good - the best of us alchemise caffeine and low GI sugars into code. Exercise such as walking fast or using ten fingers when typing gets a thumbs-up too.
10. Be a touch-typist: Pecking at the keyboard during an interview is not a good look. On a bad day it can feel excruciating working with a two fingered typist. We’re simply more effective when our fingers (almost) keep up with our thoughts. Even for 30-second bursts of typing.