← Back to blog

Redson Dev brief · COMPLEMENTARY MATERIAL

PODCAST#AI#Product#Dev

AI Can Write Code. Why Isn’t Software Better?

a16z Podcast · September 28, 2026

The prevailing challenge in modern software development isn't just generating code faster, but evolving its fundamental capabilities beyond static instruction. This podcast episode delves into the idea that while AI can readily write code, the resulting applications often remain structurally conventional, simply accelerating existing paradigms. It proposes a shift towards embedding intelligence *within* the software itself, enabling programs to interpret intent, make probabilistic decisions, and adapt dynamically, rather than merely executing pre-defined rules or producing text for human interpretation. The core argument highlights reliability as the crucial factor for making AI truly programmable, paving the way for a new era of probabilistic software. This perspective directly impacts how developers, founders, and operators should approach their next generation of products and internal tools. For instance, an indie SaaS founder in Portland, Oregon, building a niche project management tool, could move beyond traditional task states. Instead of just "to do," "in progress," and "done," their software could infer priority shifts based on communication patterns, stakeholder availability, and resource constraints, suggesting optimal task sequences rather than requiring manual adjustments. Similarly, an internal IT team at a mid-sized financial firm in Charlotte, North Carolina, could deploy an "intelligent" access management system. Instead of rigid role-based rules, this system could probabilistically evaluate access requests for sensitive documents based on real-time project context, user behavior anomalies, and a deep understanding of data sensitivity, reducing bottlenecks while enhancing security. For a logistics startup in Chicago, Illinois, optimizing delivery routes, this means moving past static routing algorithms to a system that intelligently anticipates traffic fluctuations, weather impacts, and even customer availability using live data to dynamically reroute drivers without human intervention, ensuring more reliable and efficient deliveries. To begin exploring this paradigm, consider a small, contained problem within your current operations or product. Identify one decision point that currently requires human judgment or a rigid "if/then" rule, where a degree of uncertainty or inference could lead to a better outcome. Try to model that decision as a probabilistic one, mapping out the inputs that inform it and the range of possible outcomes. Then, consider how you might build a micro-service or a small feature that could start to learn and make these probabilistic calls, even if initially with low confidence, providing suggestions or partial automations that humans then approve.

Source / further reading

Learn more at a16z Podcast →