Why One Developer Turned Repo Documentation Into a Career-Long Discipline

A software developer describes how rapid team growth at an EHR startup in 2012 pushed him to systematize project documentation as a repeatable professional habit. Rather than limiting documentation to a basic README, his approach covers setup instructions, architecture notes, runbooks, and key decision rationale to help any future maintainer hit the ground running. Colleagues at his current employer informally call the practice 'John-ifying a repo,' recognizing the clearer entry point it creates for new contributors. The developer argues the real tension around documentation is not whether people read it, but knowing when to trust it — since docs can become stale, incomplete, or inaccurate over time. He frames thorough handoff documentation less as a courtesy and more as a way to preserve context that source code alone cannot capture.