Types Are a Checkpoint for AI Code
One standard for accepting or rejecting AI-written TypeScript: pin down what the types own, drop the over-engineering, and leave compiler evidence behind.
Technical articles crafted for a wider audience, covering the problem, context, solution, and outcome.
One standard for accepting or rejecting AI-written TypeScript: pin down what the types own, drop the over-engineering, and leave compiler evidence behind.
How to review an AI that produces different code every time by layering deterministic instruments — tests, linters, scripts — and splitting the work into small reviewable units through modularity, explained step by step
Why AI-written code goes quietly wrong, and the three pillars that fix it: reproducing correctness as tests, engineering the harness, and adding self-feedback plus an independent reviewer
A beginner-friendly build log of a local graph view that shows til/knowledge documents centered on the current one — from BFS data design to the force simulation, orbital layout, star animation, and fullscreen