Evolution, not Disruption!

We’re not facing disruption, we’re witnessing evolution.

The history of human-computer interaction tells a fascinating story. We began with human “computers” doing calculations by hand, then moved to room-sized machines with tape reels and punch cards. We graduated to CPUs and machine language, then created high-level programming languages that could translate our symbolic logic into instructions machines could understand.

Today, we’re realising a decades-old dream: communicating with machines in natural language. Though let’s be honest, COBOL and SQL were pretty successful attempts at this too!

This isn’t something to fear. We’re simply entering the next chapter where humans must learn to articulate intent rather than implementation.

Specification-driven development is becoming reality. We’ve evolved from programmers to instructors, and frankly, it’s exciting.

What’s particularly interesting is how this aligns with what Donald Norman described in “The Invisible Computer.” He argued that technology should disappear into the background, becoming invisible tools that enhance human capability rather than forcing us to adapt to them.

AI-powered development is finally making this vision real. We’re no longer wrestling with syntax and implementation details, we’re focusing on what we actually want to achieve.

And here’s something crucial that gets overlooked in all the doom and gloom about AI: as Shane says, it’s not killing agile software development, it’s supercharging it. Think about it. Continuous delivery of value? AI helps us prototype and iterate faster than ever. Responding to change? We can pivot and adapt requirements in real time. Fostering collaboration and communication among humans? AI handles the grunt work, freeing us to focus on the creative problem-solving and stakeholder conversations that actually matter.

But here’s the challenge that keeps me thinking: Right now, we need deep technical expertise to validate, correct, and trust what AI produces. Those of us who spent years coding without AI assistance have the foundational knowledge to spot when something’s off.

What happens to the next generation of developers who will start their careers in an AI-heavy world? How do we ensure they develop the critical thinking and technical depth needed to be effective instructors rather than just prompt writers? Isn’t perhaps AI making a compelling case for hiring junior developers to develop into expert instructors/validators?

Originally posted on LinkedIn.