Not long ago, most conversations about AI in software development cantered on how it could help engineers write better code and become more productive.
Today, the conversation is shifting. As AI continues to eliminate many entry-level and low-level engineering tasks, we're increasingly hearing that "writing code was never the main job" as though experienced engineers didn't already know that.
That's why I find it interesting when people assume that an AI capable of reasoning through large codebases, architecture decisions, and complex workflows somehow won't be capable of creating and maintaining effective systems, the very systems many software engineers are paid to design today.
The reaction to Fable and the concerns raised about its capabilities are a reminder of how seriously advanced AI systems are already being taken. When a technology generates that level of attention, scrutiny, and debate, it's worth paying attention to what it may be capable of in the near future.
Whether we like it or not, the scope of what AI can do continues to expand. Dismissing that possibility outright feels less like scepticism and more like denial.
The question is no longer whether AI will influence software development. It already is.
The real question is: How do engineers adapt, evolve, and position themselves to create value in a world where intelligence is becoming increasingly accessible?
The future likely belongs to those who learn to work alongside these systems, not those who assume they're safe from them.
