What do you do if your job security as a late career application developer is at risk?

1. Sharpen your primary skills and become an expert in it. Understand the use of frameworks, tools, programming and different software design principles, design patterns etc. Gain expertise in software architecture and understand the importance of software design for better utilisation of computer, memory and I/O to achieve high throughput and better performance. Learn best practices in your domain for code, design, testing, reviews and devops etc. 2. Keep the documentation updated as per the current version of the code. The documentation is very helpful for the developer, QA , designer, Architect and helps a new member of the team to learn the system faster. 3. Increase breath of your skills and learn about relevant skills for your role

Make stuff regularly and show them to others. Making things is fun and rewarding especially when it's something you want. Showing your work forces you to finish your projects. Sprinkle tech or tools every time you make something new, if you're happy doing that, you'll learn how to learn and that's invaluable in any job market any time any where.

In our field, technology is always changing, but there are some enduring problem solving techniques that live on in every new technology generation. The happiest old developers I've had the privelege to work with were always curious, and happy to learn new ways to apply age old problem solving techniques. With age comes wisdom of the many mistakes you've witnessed or been a part of in the past. But that wisdom is useless if you can't apply it in the tool sets and modern frameworks.

Some ways to get started: One tactic I've found effective is dedicating a specific time slot at work each week to focus solely on learning. In my experience, online courses have been invaluable for acquiring new skills. One thing I have found helpful is joining relevant communities or forums where professionals discuss industry trends, share resources, and offer support.

I call networking, "Increasing your surface area for Luck" the best way to network is to simply "Be Useful" whenever you can. This is why if I see a LinkedIn Contact turn green looking for work, I always take 15 minutes to search internal job recs and send them some leads. We all tend to remember the people who were willing to help us out, especially if they go out of their way to help when we need it most.

Some ways to get started: One effective strategy I've found is attending industry conferences or meetups. These events offer opportunities to network with professionals in your field and stay updated on the latest trends. In my experience, engaging in online forums such as Stack Overflow or GitHub discussions has been valuable. These platforms allow for knowledge exchange and networking with a global community of developers. One thing I have found helpful is joining local tech groups or professional associations. These organizations often host events, workshops, and networking sessions, providing opportunities to connect with industry peers and potential employers.

Pivoting as it’s known today is sometimes necessary. Something to remember about risk is that it’s relative. There can be risk in taking a new role or in staying put. You may have to take a step backward or sideways to return to where you feel you belong. When your position is at risk, your old comfort zone is gone. But that can energize you for what you now need to do. Remember not to disparage wherever you land because someone needs it to work.

There is an extremely pithy book "Who moved My Cheese" that I'll admit, I hated when I first read it years ago. But the theme is, when things change, see the change for what it is, then find a way to find your happiness in the new landscape. Dwelling on how things were, won't help you find happiness. I'll admit, I do try and postmortem a bit, and see if there are patterns that I didn't see prior to the change that could have given me more warning. Ultimately we aren't in control of the universe, we just control ourselves.

Some ways to get started: One way I've found effective is actively seeking opportunities at work to engage with new methodologies like Agile or DevOps. In my experience, being open to different roles, like project management or business analysis, has helped me adapt to change while leveraging my expertise. One thing I've found helpful is staying informed about industry trends through online resources and professional networks. This proactive approach prepares me to embrace new opportunities in the evolving technology sector.

I recommend side projects or open source too. You need the ability to own making things from idea to some thing people can use. The skill of taking an idea and making something will always be valuable, no matter your age in the market place.

Some ways to get started: One strategy I've seen work is utilizing downtime at work to explore freelancing or consulting opportunities. This allows you to test the waters without fully committing. In my experience, leveraging my expertise to offer consulting services has been rewarding. It not only provides additional income but also allows me to contribute my insights to various projects. One thing I've found helpful is utilizing freelancing platforms like Upwork or Fiverr to find short-term projects. These platforms offer a wide range of opportunities and can help expand your professional network.

Some ways to get started: One approach I've seen is using lunch breaks or after-work hours to mentor less experienced developers. It's a way to give back to the community while reinforcing your own knowledge. In my experience, teaching part-time at a coding bootcamp has been fulfilling. It keeps me updated on emerging trends and deepens my understanding of the subject matter. One thing I've found helpful is networking with local coding bootcamps or educational institutions. They often welcome experienced professionals as mentors or instructors, providing an opportunity to share knowledge and expand your career horizons.

Testing as a QA or Software Developer in Test can add a perspective on code that has become quite relevant nowadays. It can add some breadth to a developer’s tool chest. As always, consider how long to remain in such a role and if there are new possibilities afterwards.

Some ways to get started: One strategy I've found effective is volunteering for cross-functional projects at work. It's an opportunity to learn about different aspects of application development beyond coding. In my experience, taking online courses or workshops in project management, UX design, and data analysis has been beneficial. These skills have not only diversified my expertise but also made me more valuable to my team and organization. One thing I've found helpful is seeking mentorship from colleagues who possess expertise in areas outside of coding. Their guidance and insights have been invaluable in expanding my skill set and understanding of the business side of application development.

If you believe your position is at risk, consider how your employer views its employees. Are you their value point or do they consider you an expense? If the former, you may be able to work more with them in making any transition you may find necessary. If the later, focus on relationships with people you trust and respect within the organization. Often birds of a feather…well, you know.

"Get busy living or get busy dying." to stay valuable in the market place, you need to be able to pick up new tools and be a sage voice to the younger generation. Every team is simply looking for good people who do great work.