AI coding platforms work best when you treat the AI as a junior engineer, not a replacement for your thinking. Break problems into small tasks, plan in Markdown before coding, and keep your context window lean - accuracy drops sharply past 50% capacity. Never debug in the same chat where you built the feature; the AI is biased by its own logic. For existing codebases, reference well-written code as examples. For new projects, define strict guardrails early - without them, the AI makes hundreds of arbitrary decisions that compound into a mess. The blog dives deep into all the patterns that work, the anti-patterns that silently kill your codebase, and strategies for both brownfield and greenfield projects - each illustrated with detailed diagrams. You stay the architect; the AI executes.

Marketplaces are about to get weird. With Pedro Chaves and Donné Stevenson: agents picking your house, negotiating deals, even talking to other agents for you. Less browsing. Less choice. More automation. Convenience… or giving up control?

A new paradigm is emerging for building applications that process large volumes of data, run for long periods of time, and interact with their environment. It’s called Durable Execution and is replacing traditional data pipelines with a more flexible approach. Durable Execution makes regular code reliable and scalable. In the past, reliability and scalability have come from restricted programming models, like SQL or MapReduce, but with Durable Execution this is no longer the case. We can now see data pipelines that include document processing workflows, deep research with LLMs, and other complex and LLM-driven agentic patterns expressed at scale with regular Python programs. In this session, we describe Durable Execution and explain how it fits in with agents and LLMs to enable a new class of machine learning applications.