Skip to content

Measure "flow state" #797

@muety

Description

@muety

Developers will know that flow state is usually the most productive and satisfying way of working, even though it's hard to get there due to distractions and interruptions. According to the "23 minutes rule" it takes between 20 and 25 minutes to get back into flow after an interruption (referring to the study linked in this blog post).

I'd like to give users a (very rough) measure of their percentage of "flow state" within a certain interval, measured in percent.

My idea is to simply take all > 23 minutes-long consecutive coding segments, subtract 23 minutes and consider the remaining time as flow time. Divide this by total coding time to get the relative percentage.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions