r/softwareengineer • u/Exciting_Pea521 • 10h ago
I think we're overestimating what AI brings to software engineering (beyond productivity)
​
I've been thinking about the current AI hype in software development, and I have a feeling we're sometimes confusing the ability to produce code with the ability to engineer software.
Don't get me wrong. AI is incredibly useful. It can write code faster than most developers, implement features, refactor existing code, generate tests, explain unfamiliar technologies, and automate repetitive tasks.
I actually think the most effective way to use AI right now is as an assistant.
However, I think there is a fundamental distinction that gets overlooked.
Writing software and advancing software engineering aren't the same thing.
Most software developers use existing concepts to solve real-world problems. We use established algorithms, architectural patterns, programming paradigms, design principles, and technologies.
But where did those concepts come from?
They were developed by software engineers, researchers, and computer scientists who questioned existing approaches, identified limitations, and came up with new ways of thinking about software.
Think about object-oriented programming, functional programming, relational databases, distributed systems, type theory, and the many architectural concepts we rely on today.
These weren't simply implementations of existing ideas. They fundamentally changed how we approach software problems.
And this is where I have some doubts about current AI capabilities.
AI is very good at using existing knowledge, combining established patterns, modifying existing implementations, and generating solutions based on what it has learned.
But I'm not convinced that this is the same as independently identifying a fundamental limitation in an existing paradigm and developing an entirely new concept to overcome it.
Can AI generate something novel? Absolutely.
Can it contribute to research? Certainly.
But can it consistently demonstrate the kind of fundamental conceptual thinking that leads to entirely new engineering paradigms? I'm not convinced yet.
And I don't think we should assume that making AI better at generating code will automatically make it better at this kind of intellectual work.
There is another issue that concerns me even more: technical debt.
AI makes producing code significantly cheaper and faster. But understanding, reviewing, maintaining, and evolving that code hasn't become proportionally cheaper.
Imagine developers accepting AI-generated implementations simply because they work, pass tests, and follow existing patterns.
An implementation can be perfectly functional today while introducing unnecessary abstractions, tight coupling, duplicated logic, or architectural decisions that make future development harder.
Now imagine this happening across hundreds or thousands of changes in a project.
We could end up with codebases that grow faster than our ability to understand and maintain them.
In other words, AI might help us accelerate development while simultaneously accelerating the accumulation of technical debt.
I also think there's a long-term risk if developers become too dependent on AI for implementation without understanding the underlying concepts. We might become increasingly efficient at applying existing knowledge while investing less effort in understanding, questioning, and advancing it.
My current position is simple:
AI should help us implement good engineering decisions, not replace the thinking required to make those decisions.
Use it to accelerate development, explore alternatives, automate repetitive work, and improve productivity.
But architecture, conceptual design, technical trade-offs, and engineering responsibility still require genuine understanding.
I'm not saying AI will never reach a different level. I just think we're too quick to assume that better code generation means better software engineering.
What do you think?
\- Are we confusing code-generation capabilities with actual software engineering capabilities?
\- Do you think AI will eventually be able to create fundamentally new software concepts and paradigms, rather than primarily building upon existing knowledge?
\- Are we underestimating the technical debt that AI-assisted development could introduce?
\- Could excessive dependence on AI eventually weaken developers' ability to reason about software architecture and design?
I'd especially like to hear from experienced software engineers, architects, programming language researchers, and people working on foundational computer science.