Finish the tickets, but don't close the tickets ;)

Isn't this the standard practice? :)

I developed the habit to announce all changes in my service on Slack when deploying to production, even seemingly invisible ones, and that helps not to forget the tickets after writing the code. But team lead still finds some finished but unclosed ones on each backlog GC run.

This is the way

I used to feel really bad about this until I learned a lot of other programmers do the same thing. Work hard and fast for a little while when you’re motivated, relax a lot when you’re not.

And hope you’re more motivated than not?

Yeah, more or less. I have to find ways to kickstart motivation. Probably why I like owning my own business. xD

Interesting. I fell into a hopeless pit of despair and got far less work done as a result. I need my soma fix.

Oh no. Your burn down chart won’t look right. They’ll crucify you for that and ask you to explain it for sure.

Same. It's probably just a coincidence though. Because if it weren't, I'd have an addiction I'd need to confront.

I was so productive I managed to finish the work inside of a day that I've been having trouble with the past two weeks. Maybe HN should have planned blackouts? :D

Just explain that it's unsustainable regardless.