Engineers should prepare for disruption

In his article on Medium, “Software engineers will be obsolete by 2060,” Dan Auerbach compared today’s well-paid software engineers to the telegraph operators of the 19th century—essential now, but destined for obsolescence as technology advances. For the telegraph operators, it was the invention of the telephone that marked their downfall. As a software development business owner, I couldn’t agree more. The skills we hired for back in 2010 have already been replaced by smarter frameworks and more efficient tools. But the real question is: what is the ‘telephone’ of the IT age?

Many articles paint broad strokes about the future of software engineering, predicting that AI and automation will slowly render human engineers redundant. But what are the transitional phases? What’s the roadmap from where we are now to a future where software engineers are no longer needed? While we’re seeing promising technologies—artificial intelligence, machine learning, blockchain, and the Internet of Things (IoT)—these are mostly fringe experiments, not yet ready to replace the expertise and complexity that engineers bring to the table.

One thing is clear: software is becoming more complex, not simpler. This complexity, paradoxically, is what both sustains and threatens the role of software engineers. The sheer volume of data, the increasing interconnectivity of devices, and the constant push for user-friendly experiences means that engineers are needed now more than ever. But at the same time, the very forces pushing this complexity are working on solutions to eliminate the bottlenecks engineers represent. Automation, AI, and smarter tools are aimed at reducing human involvement in coding.

None of us know for sure what the next major disruption will be. However, a few trends are undeniable:

  1. We’re moving toward rapid development cycles, emphasizing speed over perfection.
  2. The focus is increasingly on interconnectivity and seamless integration.
  3. Software design is becoming more user-centric, yet continues to struggle with over-design, adding complexity for the sake of feature richness.

As users, we’ve come to accept certain frustrations:

  • The app you sign up for today won’t deeply integrate with the tools you already use.
  • The data you create within software is often locked in and not easily accessible for use elsewhere.
  • The way we interact with software changes so quickly that learning a new interface feels like a regular part of daily life.

While engineers play a crucial role in managing these challenges, we can’t ignore the undercurrents suggesting that we are heading toward an era where much of the work engineers do today will be automated or absorbed by smarter systems. The future might not be completely free of engineers, but the role will evolve dramatically—and those who don’t prepare for that disruption could find themselves as obsolete as the telegraph operator.

For engineers, the best way to prepare is to stay adaptable. Embrace learning new skills, understand the potential of emerging technologies, and anticipate how these trends will shape the future of software development. Disruption is coming—it’s just a matter of when.