I usually have 4-5 lines per day, where some days have 15 (rare, but there are those big days).
I don't give the report in slack, since github has track of when stuff was committed (I commit at the end of the day), if people need it, it's on github.
It's great for standups, because I usually forget what I did yesterday. It's also great for some company tax reductions, so it's appreciated!
Last but not least, I capture breakthrougs and decisions in there, as well as learning, so I can refer to it various months later and tell people exactly what I was doing a certain date.
At some point people asked "why this wasn't already done, what were you doing in August last year"... And I was able to clearly explain what I was doing in August and why things were not prioritized.
Overall, great win!
Just to clarify, I didn't come up with this idea myself, it was suggested to me on the Eventide Slack https://eventide-project.org/#community-section Apparently it's a common practice in engineering (should be in software engineering too!), I currently follow this log structure: https://github.com/eventide-project/project-status/blob/mast...
Can you explain what you mean by company tax reductions? I'm confused how that relates with keeping a worklog.