Documentation for the you who forgot
I came back to a project after 14 months and found two notes I'd left myself, in the same file, in the same voice, and one of them saved me 40 minutes and the other cost me an hour and a half.
6 posts filed under Documentation, newest first.
I came back to a project after 14 months and found two notes I'd left myself, in the same file, in the same voice, and one of them saved me 40 minutes and the other cost me an hour and a half.
I took over a project in June where the previous developer had left properly, with everything written down, and it was so unusual that I spent the first morning slightly suspicious of it.
Every other document about a codebase starts drifting the moment you save it. A commit message is welded to its diff forever, which makes it the only one that can't lie to you.
A client should own their domain, their hosting, their repository, their analytics and every account their business runs through, and in three years I have met perhaps two who did.
I lost a day changing a phone number on a site I built myself, and not one minute of that day was spent on the phone number.
Everything written about design systems this year comes from teams of forty with a five-year roadmap. I build storefronts on a six-week clock. Sorting the practice from the apparatus.