
10/11/2022
What this post added
This post introduces a methodology for writing and editing code with minimal reading by leveraging build errors and the type system. It details strategies for finding code entry points by searching for user-visible strings, making initial breaking changes to trigger build errors, and climbing the callstack to resolve these errors. It also outlines how to update recommended code during the 'downswing' by relying on linters, type system enforcement (e.g., tagged unions, exhaustive switches), and unit test failures. The post advocates for codifying important checks in linters and the type system rather than relying on comments.