Software Has Always Been Different
Software engineering has often been different to other engineering disciplines.
In most fields, there’s clearer separation. Someone designs it. Someone manages the build. Someone constructs it. Someone signs it off. In software, it’s often been the same person.
You’re the architect, the project manager, the builder, the bricklayer. You design the system, write the code, think about tradeoffs, deploy it, debug it, and then wake up when it breaks.
Parts of that are getting simpler. Tooling is better. Infrastructure is abstracted. The grunt work is automated.
But the People Don’t Change
But the people who gravitate toward software aren’t just there because they like typing code.
People in software have extremely high tolerance for complexity. Strong problem solving ability. Critical thinking. A lower tendency to jump to convenient but incorrect conclusions.
That cognitive profile doesn’t disappear just because parts of the job get easier. If anything, it becomes more important.
The tools may lay more of the bricks for us. But deciding what to build, why it should exist, and how the pieces fit together, that’s still deeply human work.
It becomes about leverage. AI is a multiplier. Like financial leverage, it amplifies whatever sits behind it. Good judgment scales. So do bad assumptions.
Developing AI fluency, through experimentation, individually, within and across teams, is how you tilt that leverage toward upside instead of risk.