Endpoint Systems

I published: Parsing JSON is a Minefield 💣 seriot.ch/parsing_json.p… in which I could not find two parsers that exhibited the same behaviour

at @Auth0Lab we’ve worked on fairly complex things like fga.dev and auth0.ai. always look to 1. validate as cheap as possible. before it used to be a dog and sequence diagrams or figma with a customer. now throwaway proto 2. iterate and derisk key matters 3. define principles. eg “account linking needs to be a single request, not client handled nor via extensibility” repeat. once we get to a state where we are confident, we build. we have a small team, we can decide fast, we are SMEs

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (@bcherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations Brought to you by: • @statsig  — ⁠ The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic • @SonarSource – The makers of SonarQube, the industry standard for automated code review. Proactively find and fix issues in real-time with the SonarQube MCP Server: sonarsource.com/products/sonar… • @WorkOS – Everything you need to make your app enterprise ready. workos.com Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”