Discussion about this post

User's avatar
Scott Aubrey's avatar

This resonates so much. I'm a software engineer by trade, but done time in DevOps, management and (lower) exec too, managing product managers.

I'm looking around at other software guys around me as they retreat into their own silos with only Claude and their imaginations, replacing the discovery and creation we used to do as teams with show-and-tell, where even the tell is written by Claude. I look on with a kind of despair as previously reasonable individuals seem to have convinced themselves that despite continuous ongoing efforts to corale and cajole and correct, and still missing basic issues, "self coding is over", while they pull the ladder up behind them for the next generation of software professionals.

I have been pondering what has been driving this "individualisation" of engineering again and your thoughts here make a lot of sense. I only wish there was more self awareness, and less FOMO from hype train narratives, so we can actually figure WHAT AI can actually do for our "cross-functional product development" teams, together.

Quiet Operator's avatar

The identity lens suggests a useful question for any team building its own factory. Ask, "Which part of this system exists because it solves a customer problem, and which part exists because it keeps our role central?" Writing both answers down before the next planning session makes the trade-off easier to discuss without it feeling personal.

15 more comments...

Ready for more?