I stopped writing PR descriptions. Here's what I...

I opened 6 PRs last week. I wrote a good description for exactly one of them. The rest looked like this: "fix bug" "update styles" "wip" "changes" (my personal low point) And I'm not even ashamed — I've seen senior engineers with 10 years of experience do the same thing. Here's why it happens: You just finished 3 hours of deep work. You know exactly what you changed and why. Writing it down feels like explaining a joke — the effort of articulating it kills the momentum. So you type something vag