Require team members to write documents themselves, actually read them, and give feedback to establish a high engineering bar.
Today's programming languages were designed around human productivity, so slop has already seeped throughout our code.
Boundary built BAML, a language for agents. Its visualization system makes it easier to drill down to the implementation level, while the compiler infers error types automatically to preserve safety at the language level.
The argument that errors should be eliminated through types and language design rather than prompts stood out to me, and I agree with it.
Could design systems and UI patterns produce more consistent interfaces if they were enforced by the system rather than left as guidelines?
Analyze frequently used patterns in a codebase through AST parsing, turn them into formal patterns, and expose them through lint rules at error, warning, and info levels.
This is the moment when our codebase has the least slop it will ever have!
