3d ago · 16 min read · The first time I tried to migrate a large JavaScript codebase to TypeScript, I made the classic mistake. I planned a six-week migration project, kicked off with a team meeting, started at the top of the directory tree, and got about 4% through before...
Join discussion3d ago · 16 min read · Every developer I know has a story about dependency hell. Mine was a Friday afternoon in 2024 when I ran npm update on a project I had inherited, and the entire test suite turned red. Not a few tests. Every single test. The diff was 400 packages chan...
Join discussion6d ago · 14 min read · Two years ago I inherited a project from an engineer who had left the company. The codebase was clean. The test coverage was reasonable. The architecture was defensible. The documentation was a single README that said "TODO: write docs." There were 2...
Join discussion6d ago · 13 min read · The first public API I designed had 47 endpoints. Eight months later, 31 of them were either deprecated, broken, or quietly ignored by the only client that ever consumed them. Two were so badly named that we shipped a v2 just to rename them. One retu...
Join discussionMay 7 · 7 min read · Every project has rules the AI doesn't know about. Not requirements — those are usually in the spec. Not goals — those are in the brief. Rules: the non-obvious constraints that have accumulated through decisions, negotiations, discoveries, and hard l...
Join discussionMay 7 · 6 min read · There's a failure mode in AI-assisted work that's almost invisible until you know to look for it. Questions that haven't been answered don't stay open in the AI's working model. They get filled in. If you're working on an API design and it's genuinel...
Join discussionMay 7 · 6 min read · When you write a note for yourself, you're writing for a reader who shares your context. You know what project this belongs to. You know what decisions led here. You know which parts are settled and which are still open. You can afford shorthand, par...
Join discussionMay 7 · 8 min read · Prompt engineering has a maintenance problem. You write a careful prompt for a task you do repeatedly — synthesizing research notes, auditing link hygiene, archiving stale material. It works. You save it in a prompts folder. Three months later you ca...
Join discussionMay 7 · 6 min read · How to set up an AI-native Obsidian vault from scratch (30-minute guide) Most Obsidian tutorials focus on note-taking. This one focuses on a different problem: giving an AI coding agent reliable, traversable context that persists across sessions. By ...
Join discussion
