In this channel's material, Claude 3.5 Sonnet appears as the underlying model behind Val Town's AI assistant Townie — and as the centerpiece of founder Steve Krouse's explanation of why AI coding jumped forward in a single year. [^ebfee90b-4a43-55ab-9be2-5070c4aaefb0@0] Krouse credits three things for that leap: integration (the copy-paste loop between an LLM and a coding platform becoming one product), the system prompt (telling the model code runs in Deno JavaScript, that no server needs starting or deploying, and which platform bugs to avoid), and — in his words — the model itself: Claude 3.5 Sonnet was the most important thing that happened. [^ebfee90b-4a43-55ab-9be2-5070c4aaefb0@0] The episode also uses the model to explore two broader industry themes: - Perceived degradation and evals. Before Val Town had real evals, users reported the model getting stupider over weekends, and Krouse admits helping fuel a brief industry panic where everyone convinced each other Claude 3.5 Sonnet had degraded. Once evals existed, he could check complaints against them — and confidently say try again if nothing showed up. - Staying neutral to model progress. Val Town architected a model switcher, beta flags, usage-based pricing, and per-model prompting so it could jump when a new Sonnet shipped — the way Cursor and WebSim did. In practice they actually rolled back from the newer Sonnet because they couldn't get its prompting right, showing that harness quality matters as much as the model name. [^ebfee90b-4a43-55ab-9be2-5070c4aaefb0@0] Use this term when the material discusses which model powers an AI coding tool, model-driven leaps in capability, or the architecture needed to benefit from a new model without rearchitecting a product.