Blog
AI-assisted development, documentation, and building in public.
You can build an entire SaaS in a weekend with Claude Code or Cursor. The problem hits on Monday morning when you open the repo and have no idea where you left off. Here is why that happens and what we built to fix it.
DocForMe generates doc pages from your actual code, not from what you wrote in a README. This is the story of how we designed the sync pipeline, what we got wrong, and how smart diffing cut our API costs significantly.
Every vibe coded project has them: TODO comments, placeholder copy, disconnected routes, functions that return nothing. We built a pass that finds all of them automatically and it is harder than it sounds.
AI coding tools are getting better at writing code. But they all have the same blind spot: they forget everything between sessions. We think the real bottleneck in AI assisted development is not generation speed. It is context restoration.
We launched DocForMe with no landing page, no marketing, just a tweet. Here is what happened: the signups, the feedback, the things that broke in production, and the one insight that changed how we think about the product.
The hardest part of shipping a side project is not writing the code. It is knowing when it is actually ready. We built a scored audit that reads your codebase and tells you exactly what would embarrass you if a user found it.
The README is the most dishonest file in any repo. It describes the project as it was the day you wrote it, not as it is today. Documentation that is not automatically kept in sync is worse than no documentation at all.