A Real Problem Is Not Automatically an Urgent One
The problem was real at every stage. It still was not urgent enough to buy. What 50+ conversations, three pivots, and Maat taught me about validation.
Read postWriting
Articles about backend systems, AI, entrepreneurship, and engineering teams.
The problem was real at every stage. It still was not urgent enough to buy. What 50+ conversations, three pivots, and Maat taught me about validation.
Read postI checked Cal.com's own documented architecture rules against their code, then pointed the same tool at a problem no linter can see: code that means two different things.
Read postPR reviews help with code quality, but they can't catch every architectural issue. Here's why.
Read postYou can write a perfect ADR and in 18 months nobody follows it. The question is not how to document better. It is what you do with the documentation after it is written.
Read postGitClear's data shows code cloning is up while refactoring is down. That matters because duplicated code creates coupling, and refactoring is the work that forces teams to reconcile it.
Read postI tested Claude Code (Opus 4.6) and Codex (GPT-5.4 xhigh) on creating and extending code and detecting implicit coupling in an existing codebase.
Read post