Posts

The speed of AI-generated code has broken the traditional software review cycle. We have reached a point where the speed at which agents produce code far outstrips the pace at which humans can verify them. If our primary mode of accountability, manual inspection, is destined to fail, how do we maintain the safety and reliability of our systems without slowing down? History offers us a lifeline. Other industries, from global high-frequency trading to large-scale pharmaceutical manufacturing, have faced similar dilemmas when throughput exploded....

The software development industry is currently navigating a crisis that mirrors other shifts in industrial history. For many years, the primary mechanism of accountability in technology was the peer review process. This is a “ceremony” in which a human engineer manually inspects another’s work. This “craftsmanship” model relies on the assumption that human output was bounded by human temporal and cognitive limits, allowing for 100% manual oversight. However, the emergence of AI coding agents has been disrupting this equilibrium....

Originally published on the Platfform Engineenring blog. There’s a powerful and relatable story that plays out in many organizations. It often starts with a conversation, perhaps one with a new director of engineering, flush with enthusiasm and a grand vision. They detail a future-state “modern platform,” complete with the latest and greatest tooling, all designed to make the company a genuine technology leader. This vision is often driven by a core belief - an unspoken assumption - that “if you build it, they will come....

The other day, I was discussing system architecture with some colleagues. The topic of rate limiting came up, and a rather contentious point was raised: Is rate limiting an anti-pattern for internal services? One of my colleagues argued that if internal services require rate limiting, it’s a sign of underlying architectural issues. Well-designed services, he contended, should scale automatically without needing such restrictions. My initial reaction was strong disagreement. I’ve implemented rate limiting and seen firsthand how beneficial it can be in preventing cascading failures and protecting against unexpected behavior....

The software development landscape has long sought the holy grail of universal solutions, echoing the “write once, run anywhere” promise of Java. This allure has seeped into platform engineering, where the notion of a one-size-fits-all platform - a singular entity capable of addressing the diverse needs of every team within an organization - has gained traction. However, like many oversimplified ideals, this approach has many pitfalls that can impede innovation, scalability, and overall organizational effectiveness....