Post by Joshua Lewis

AI isn’t here to kill code – it’s here to make code, and the people who write it, more valuable. Rob Thomas' article cuts through the “AI vs developers” noise and gets to the real issue: not whether AI will write code, but what we want humans focused on when it does. From an IBM standpoint, a few points really stand out: - AI is becoming a core part of the software supply chain, not a bolt‑on gimmick. The leaders will be the ones who can industrialise this – models, platforms and workflow – in a governed, repeatable way, not just ship flashy demos. - The real upside is shifting human judgment upstream. Getting engineers to spend more time on problem framing, architecture and non‑functional requirements, and less on boilerplate, is exactly the kind of productivity gain enterprises have been chasing for years. - Guardrails are non‑negotiable. In complex, regulated environments, “AI that can code” isn’t enough; it has to be grounded in trusted data, observable in production, and subject to the same engineering discipline as any other critical system. At IBM, this is where we are putting our energy: - Using AI to accelerate delivery and improve developer experience while strengthening governance, security and reliability. Viewed through that lens, the question stops being “Will AI replace developers?” and becomes “How fast can we redesign our engineering practices to harness this new capability? Ana Arran Zoë Natasha Andrew Chris Ayal Leon Lee Ryan Chema Dushmanta Lewis Gary Finbar Brendan Andrew Andy Charlotte Bill Kylie Rebecca James Karen Jessica Nick Nick Kareem James Simon #AI #Development #IBM #Amplify #KillCode