Engineering & AI
Are Software Engineers Becoming Obsolete?
Why learning to code still matters in the AI era—and why engineering judgment is more important than typing speed.
The wrong question is about typing
If software engineering were only the act of producing source code, better code generation would make the profession straightforward to automate. But source code is the visible output of a much larger process: deciding what should happen, what must never happen, and how to know the difference.
A system can compile and still violate an important business rule. A plausible implementation can leak data between customers. An elegant algorithm can be the wrong algorithm for its workload. These are engineering problems, not typing problems.
Fundamentals give you a way to disagree
Understanding data structures lets you question a performance claim. Understanding concurrency lets you notice a race condition. Understanding architecture lets you distinguish a useful boundary from an unnecessary abstraction. Without those foundations, reviewing generated code becomes an exercise in recognizing familiar shapes.
Use AI to extend your ability to build, not to outsource your ability to judge.
Practice before you delegate
Choose a small problem such as Two Sum. Define its contract. Work through examples on paper. Implement the direct solution. Analyze its cost. Then use an assistant to suggest an alternative and compare the assumptions. This sequence teaches you to evaluate rather than merely accept.
Responsibility does not move with the prompt
The person shipping a system remains responsible for its access controls, correctness, dependencies, and operational behavior. An assistant cannot approve your customer's privacy boundary. It cannot establish a requirement you never clarified. It cannot make an unreliable benchmark representative.
A more deliberate workflow
- Write the requirement and constraints in your own words.
- Ask for options, including their tradeoffs.
- Implement or inspect one option at a time.
- Test the failure paths, not just the happy path.
- Explain the result without relying on the assistant's explanation.
The useful question
Instead of asking whether engineers are obsolete, ask which parts of your judgment need strengthening. The tools will keep changing. The habit of understanding the systems you build remains useful.