@mattpocockuk: Less "let me write tests to catch the next time that error happens" More "let me make that class of error impossible wi…
Summary
Matt Pocock shares a developer philosophy: rather than writing tests to catch the next occurrence of an error, aim to make that class of error impossible through better design.
View Cached Full Text
Cached at: 08/11/26, 11:50 AM
Less “let me write tests to catch the next time that error happens”
More “let me make that class of error impossible with a better design”
Similar Articles
@mattpocockuk: The more I replace plans with prototypes, the better the outputs Who'd have thought that low fidelity prototypes were b…
Matt Pocock argues that replacing plans with low-fidelity prototypes leads to better outcomes, countering the trend of detailed specifications in software development.
@mattpocockuk: "No tautological tests"
A tweet criticizes the AI model Opus for adding excessive unit tests for simple constant strings, highlighting issues with tautological testing in AI-assisted development.
@nateberkopec: Prompt I use a lot: "how can I pokayoke this so this kind of error never happens again" pokayoke is using simple, low-c…
A developer shares a prompt technique inspired by poka-yoke to prevent errors by making mistakes impossible to occur.
@mattpocockuk: This is really smart. There are definitely a set of rules that are too complex to lint deterministically that feel wast…
The tweet discusses using Jev as a fuzzy linter to handle complex coding guidelines that are not suitable for deterministic linting, with examples like useEffect and comment management.
@mattpocockuk: mattpocock/skills prompt of the day: /codebase-design Take a look in the repo for shallow modules, applying the deletio…
Matt Pocock shares a prompt of the day: /codebase-design, a skill that scans a repo for shallow modules and applies the deletion test to remove unnecessary abstractions.