When it was just you and you were a bulletproof superhero, you could remember it all.
You could look at code you wrote six months earlier and you knew exactly what it did and why you wrote it that way.
A bit of time has passed since then. Youâ??ve hired new people. Because you didnâ??t write good technical documentation back then (or didnâ??t keep it up to date), there are many mysteries about your business buried deep inside the heads of your most senior, most expensive staff.
And now, they’re being interrupted repeatedly with every new hire because the new person needs the knowledge stored in the heads of the â??old onesâ? in order to do their job and learn your business.
You want a new programmer to hit the ground running. To become as productive as possible as quickly as possible.
Think back to the last new person you hired. Remember that ramp-up period?
Now imagine hiring three or five at once. Just try to get something productive done while they are getting up to speed. You (and whoever is managing them) probably have other tasks to do, perhaps very high ROI tasks. Without strong technical, application/market and process documentation, those tasks are going to get incessantly interrupted with things that should have been documented.
Sure, you’ll get brilliant questions that you might not have foreseen. The other 912 questions likely could be answered in your internal wiki or other documentation. Or you could enjoy their visits to your office, their emails, IMs, texts and phone calls, while pondering the time they’re wasting by getting you them both out of the zone every time they have questions.
PS: Just because you aren’t a programmer or don’t have programmers doesn’t mean you’re immune to this.