I used to work at a place that required daily progress reports on tasks (this was before agile took off so ‘daily standup’ wasn’t a thing.). So I wrote a script to schedule my git commits throughout the week (so that I had at least one a day), and every afternoon it would pull my git history, generate a summary, and email it to my manager.
He knew it was automated and hated me for it but I had the most consistent and detailed reports. On the upside, it really trained me to make good commit messages. On the downside It really instilled me with a strong “burn the building down” kind of vibe that persists to this day.
I used to work at a place that required daily progress reports on tasks (this was before agile took off so ‘daily standup’ wasn’t a thing.). So I wrote a script to schedule my git commits throughout the week (so that I had at least one a day), and every afternoon it would pull my git history, generate a summary, and email it to my manager.
He knew it was automated and hated me for it but I had the most consistent and detailed reports. On the upside, it really trained me to make good commit messages. On the downside It really instilled me with a strong “burn the building down” kind of vibe that persists to this day.