Writing my own performance review honestly, for once
Listing what I shipped is not the review. Listing what changed for other people is.
collaboration
6 posts
The meeting that should have been a pull request, and vice versa
Decisions need synchronous time; proposals need written artifacts.
The onboarding doc that doubled as a test of our own setup
If a new engineer cannot get running from the doc in a day, the doc is not the problem.
The bug was in the requirements, and three people implemented it faithfully
Correct code against a wrong spec passes every test.
An estimate is a distribution, and you reported the mode
Two weeks means the most likely case. What anyone planning around you needs is the spread.
The code review that should have been a conversation
Forty comments on a pull request is a design disagreement wearing a review costume.