All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Three Years In: A Senior Engineer's Reflection on AI's Impact on the Software Development Role

By

ColinEberhardt

8h ago· 13 min readenInsight

Summary

A senior engineer reflects on the long-term sustainability of AI tools in software development, three years into deep organizational adoption. The author critiques both the overly optimistic "AI made me 30% more productive" narratives and the vendor-driven architectural perspectives, arguing they miss the human reality of what it's like to be a senior engineer in an AI-heavy environment. The piece questions whether the traditional senior engineer role still makes sense given the changes AI has brought to workflows, responsibilities, and team dynamics.

Key quotes

· 2 pulled
A lot of what's been written on this topic falls into one of two camps: the 'AI made me 30% more productive' piece, usually written by someone six months into using the tools and often by a consultant who doesn't have a job to actually do, and the architectural piece about how AI changes the SDLC, which tends to be written from a vendor perspective and skips over the human reality.
I'm interested in something else: what it's actually like to be a senior engineer in an org that's gone deep on this, three years in, and whether the shape of the role still makes sense.
Snippet from the RSS feed
Jamie Hurst - Software and System Engineer, Enthusiast of Terrible Cars

You might also wanna read