Most devs are terrible at defining when the workday actually ends.

We close the laptop, but our mind keeps running. There’s always the feeling that we could have squeezed in one more commit, fixed one more bug, or read one more article.

This constant pressure to “do more” is a shortcut to burnout. Your nervous system stays in alert mode when it should be recovering.

What worked for me was defining Daily Minimum Standards.

This concept comes from Dr. David Maloney, and it completely changed how I see productivity.

I stopped asking:

“How much can I squeeze out of this day?”

And started asking:

“What’s the minimum ideal progress for me to feel satisfied today?”

This shifts the focus from intensity to consistency:

• Learning a new stack: 30 focused minutes, not 4 straight hours.
• Side project: deliver one small component, not clear the entire backlog.
• Refactoring: clean up one class, not the whole module.

When I hit that minimum, I give myself permission to stop. Everything after that is a bonus.

You need a “Definition of Done” for your day, not just for your Jira tickets.

Consistency compounds faster than occasional heroism.