We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is tr…↗

Everyone at tldraw builds internal tools, even the non-technical employees. In the process, Spencer, our US sales lead, has learned a few things about getting your PRs merged. Here are his takeaways: tldraw.dev/blog/non-techn…↗

Why Software Factories Fail: Turning the lights back on This is part two of [Why Software Factories Fail](x.com/dexhorthy/status/2080697380379427275) - Part 3 is here - x.com/dexhorthy/status/2081797628552270027 The talk version of this post is live on youtube: […↗

Introducing /improve-react Find bad React code in your codebase, triage, and fix I've found it really effective with GPT 5.6 Sol / Fable 5 (if you have $)↗

mattpocock/skills v1.1 is out! - /wayfinder helps you plan more ambitious work than ever - /to-spec and /to-tickets replace /to-prd and /to-issues - /implement + /code-review complete the whole lifecycle - /research and /prototype help support wayfinder, or can be used independe…↗

The future of agentic coding and review is chatless Chat becomes a projection layer: logs, traces and context for o11y and audits The primary interface becomes dashboards that expose goals, progress, blockers, confidence and outcomes↗

Hot take: I think it's still important to understand the code that our agents write! In this mega thread (based on my AIE talk today), I will explain why that's the case, and show some ideas for how to efficiently understand code. Alright, let's dive in. 1/↗

1. as a mental model it is more correct to think of fable+ class models as english -> code interpreters - converts your idea into code into "correct" code regardless of problem complexity and output complexity (diff size). Fable 5 will be the worst of this new class of models 2.…↗

My heuristic is that any diff an agent generates over ~1500 lines is too big and is indicative that the problem needs to be decomposed. This is my general pattern now for feature work: 1. Try to implement the whole feature, loosely guided. I call this the "draw the owl" prompt i…↗

How are coding agents changing software engineering? Yapped for 15 minutes about new Cursor data we published, including: 1. Why lines of code is an imperfect measure of AI progress 2. Balancing intelligence/cost/speed for models 3. Code reviews with "Mega PRs" (1000+ lines)↗

pierre.computer/writing/on-ren…↗

~I wrote it in Markdown first. Easy marks easy work.~ plannotator.ai↗

Learn how to use coding agents in 30 minutes! This course teaches you how to build software with agents: plan new features, fix bugs, review and test code, and more. It's 100% free and these concepts apply to any agent!↗

react-doctor helps coding agents diagnose and fix React code by performing automated code review and suggesting improvements.↗

We’re launching Codex for Open Source to support the contributors who keep open-source software running. Maintainers can use Codex to review code, understand large codebases, and strengthen security coverage without taking on even more invisible work. …↗

Claude Code on desktop can now preview your running apps, review your code, and handle CI failures and PRs in the background. Here’s what's new:↗

yesterday, i built the code review app i've been begging twitter for. - live streams change summaries as claude code works - quizzes me about changes before i commit them. - finds bugs locally -- without having to push to GitHub↗

Unpopular opinion: Current code review tools just don’t make much sense for AI-generated code When reviewing code I really want to know: - The prompt made by the dev - What corrections the other dev made to the code - Clear marking of code AI-generated not changed by a human↗

droid-code-review is a code review tool focused on reviewing Droid-related code.↗

how i build features & fix bugs with cursor: 1.select opus 4.5/gpt-5.1-codex to ask about the changes i want to make so i understand the relevant code 2.switch to plan mode and describe the changes i want to make (keep the same model) 3.reply to the follow-up questions i’m get…↗

Nice little Claude Code development kit. Lots of people have asked me about custom rules/commands for: - Code reviews - Creating code docs - Refactoring - Handing off to a new agent This has examples for all of these (link below)↗

Plannotator provides a visual way to annotate and review coding agent plans and code diffs, share them with a team, and send feedback to agents with one click.↗