Documentation for future-you
I came back to a project after a year away and found three notes I'd left myself in one confident voice, two of which saved me an afternoon and one of which cost me one.
7 posts filed under Documentation, newest first.
I came back to a project after a year away and found three notes I'd left myself in one confident voice, two of which saved me an afternoon and one of which cost me one.
The developer who left in March had put four pages in the repo before they went, and the parts that saved me were not the parts I'd have guessed.
I ran git blame on a line I could not explain and got back a one-word message with my own name on it, and the word was fix.
A client asked how the Black Friday weekend had gone compared to last year, and the chart I had to answer them with started in March.
Changing a phone number in a footer took me a full working day, and about 90 seconds of that day went on the phone number.
A client asked whether the price on the product cards could be bigger. There were two card components in that stylesheet, four months apart, both of them written by me.
I built a style guide for a client site in January and by March I was copying buttons out of a template three folders away without it ever crossing my mind to open the thing I'd built.