Why Top Developers Keep Coding After 40: Lessons from 10 Senior Engineers

21CTO community introduction: the article presents ten senior programmers over 40, all top developers who refuse management roles and continue coding.

Rob Fletcher, Senior Software Engineer at Netflix, 45

Expertise: Web development, test‑driven development, agile, Grails, Groovy, Spock, AngularJS.

"I have been coding for 16 years, joined Netflix at 42, and now write code daily. My favorite language is Kotlin; I also use Java, Scala, Groovy, and I am learning Go. I avoid management because I am a poor manager."

He stresses the importance of attitude, staying open to new technologies, and letting experience guide technical decisions.

Ebbe Kristensen, Senior Software Designer at Prevas A/S, 62

Expertise: Real‑time embedded software, configuration management, test case development, C, C++, Python, C#, Pascal.

"I have been a software engineer since 1980 and have never taken a management role because I lack competitiveness in that area. I love coding and prefer to stay on the development side."

He notes that continuous learning and a passion for programming keep him productive.

John Brothers, Senior Software Architect at Make&Build, 47

Expertise: Enterprise architecture, agile coaching, data visualization, mobile app development.

"I enjoy solving problems and constantly updating my skill set. I have used Node.js, Hadoop, NoSQL, Android, Go, jQuery, Bootstrap, Java, JMS, REST, JSON, JPA, Ruby on Rails, Perl, PHP, Python, and many other technologies."

He emphasizes being a full‑stack developer, familiarity with Unix, shell scripting, SQL/NoSQL, networking, and a willingness to learn new paradigms.

Roger Whitcomb, Software Architect & Engineer at Actian, 60

Expertise: C, C++, Java.

"I started learning computer science while preparing for a law career. I now earn a living writing well‑documented Java code and continue to develop for web and mobile despite feeling the pressure of age."

He stresses creating value for employers and staying relevant through continuous contribution.

Scott Gartner, Senior Software Engineer at Silverback Learning Solutions, 50+

Expertise: Frameworks, parsers, modeling, graphics, database subsystems, SQL, DML, DDL, LINQ, XML, SSO, web and Windows applications.

"I have been a programmer for 34 years. I keep a second résumé listing all languages and tools I have used. I avoid management and focus on architecture and coding, learning a new language every two years."

He believes that ongoing learning is essential to avoid obsolescence.

Brian Bowman, Chief Software Engineer at SAS, 56

Expertise: File system/database internals, persistent data structures, indexing, server management, DASD I/O drivers, code generation, distributed caching, large‑scale licensing systems, Cloud Analytics Service.

"My team’s average age is 50, with over 20 years of experience each. We continue to code, debug, test, and design system architecture, contributing to open‑source and presenting at conferences."

He plans to extend his expertise into machine learning.

Alec Cawley, Chief Software Researcher at DisplayLink, 60+

Expertise: Embedded systems, multithreading, drivers, communication stacks, C/C++, Java, Python, hardware‑software co‑design.

"At 62 I am the oldest developer in my company. I believe software development will remain needed for decades, and programmers must translate human needs into executable instructions."

He highlights the enduring need for skilled developers in embedded and hardware‑adjacent domains.

Victor Volkman, Senior Software Engineer at Proquest, 54

Expertise: Python, Linux, C/C++, .NET, MS Access, MySQL, TCP/IP, enterprise automation, distributed computing.

"Architecture and management are parallel tracks. In a 250‑person company, engineers can choose either. I continuously learn new environments every 3‑4 days to support business needs."

He outlines a career path that spans from MS‑DOS assembly to modern cloud services.

Kurt Guntheroth, Software Engineer, 50+

Expertise: Windows, Linux/Unix, embedded, algorithm design, C++, C, multithreading, distributed systems, telecom, security, socket programming, agile and traditional methodologies.

"Software development is a young field; tools change rapidly. A 40‑year‑old programmer must keep learning or risk obsolescence. I rate my C++ expertise at 9/10 and have authored a book on C++ optimization."

He argues that programming offers a creative, non‑political career compared to management.

James Grenning, Software Consultant, 60+

Expertise: Object‑oriented design, test‑driven development (C, C++, Java, C#), embedded software, refactoring, extreme programming, Scrum, agile, release planning, CppUTest contributor.

"I keep learning; at 62 I still love coding. I spend some time on management but always return to software development, believing that continuous learning is key to a long, successful career."

The article concludes by asking readers whether these stories inspire them and invites comments on the situation of programmers over 40 in China.