Fragments: May 14

· Source: Martin Fowler · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning · Depth: Advanced, long

Summary

The "Fragments: May 14" brief compiles observations from a Mechanical Orchard retreat on agentic programming's impact on software development. Key discussions included an LLM-powered behavioral clone of a GNU Cobol compiler in Rust, completed in 3 days with 70K lines of code, highlighting LLMs' code porting ability. The concept of "Interrogatory LLMs" for human-expert specification verification was explored. Attendees re-evaluated "Lift and Shift" legacy migrations, suggesting it as a first step due to reduced LLM-driven costs. The potential for LLMs to simplify multi-jurisdictional financial systems and automate tedious data transformation was noted. Concerns arose regarding teaching judgment to junior developers in agentic contexts, with pair programming suggested. Critiques of agentic programming emphasized using LLMs as predictable functions over autonomous agents and prioritizing architectural solutions over "skills" for reliability. The article also touches on the non-deterministic nature of AI and ethical considerations, referencing Kyle Kingsbury's "The Future of Everything is Lies, I Guess."

Key takeaway

For software architects and MLOps engineers designing new systems or modernizing legacy ones, recognize that LLMs fundamentally alter cost-benefit analyses for tasks like code porting and data transformation. Prioritize integrating LLMs as predictable functions within defined workflows rather than relying on autonomous agents, which introduce debugging complexity. Emphasize human oversight and learning from AI-generated outputs, especially in critical review processes, to ensure long-term skill development and system reliability. Consider "lift and shift" as a viable initial step for legacy modernization, leveraging LLMs to reduce costs and enable easier future evolution.

Key insights

LLMs are transforming software development by enabling rapid code porting and data transformation, but require careful integration to maintain predictability and foster human learning.

Principles

Method

Interrogatory LLM: LLM interviews human expert to verify specification correctness. Legacy migration: Lift and shift to new platform first, then evolve.

In practice

Topics

Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Engineer, Software Engineer, MLOps Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Martin Fowler.