INTRO :
What usually happens with most category-based time trackers is that we accumulate a big set of time data that is not very useful, it feels like noise and random data.
If you asked what is the most persistent general pattern that is causing delays or unnecessary complexity in our projects ?, what are the top three things that could be done to complete steps faster? What work should you delegate ?
and most importantly why some parts of our work are more complicated than others?
The data tracked using basic standard filtering is not very informative for most developers.
This is how the idea of per Rhythm tracking came from
Key insight : Hours are not equal .
Instead of absolute thinking that treats every point in time as equal , we shift to relativistic thinking per Rhythm or intensity of different chunks of time, this is especially useful for programming since the flow of the process itself is not very predictable .
This youtube video demonstrate this in action for a Vue.js solar project
If you fast forward to minute 10:12 , there is five stats calculated by the app engine
Red = most complex
Grey = no note
Yellow = average / okay
Green = in flow
Blue = easiest /delegable
we currently set the rhythms is to focus on filtering most complex and easiest points in our time, we move away from calendar deadline time predictions, and focus on capturing what is happening now.
The video example shows us that only 0.078% of 28.75 hours is actually the most important, the red dots highlight the complex parts.
That is roughly two hours out of 28hours 45 minutes, again Hours are not Equal.
On Data storage :
Minimalist release of the system is optimized to allow users to have more control and privacy of their time data , the data structure is set to encourage easy json export, and reset of logs.
We aim to progressively adjust the system to work offline, and for now we are focusing on gathering constructive feedback from our most enthusiastic users through the web release.
who should use the system ?
The usefulness of the system increases with the complexity of the project and with more combined hours, if you are working on something simple , then the app would be too much for you.
but if you are working on something complex, and like to see patterns within a year worth of work, and be prepared for increasing work demands, and like to make higher level decisions on what to delegate / automate.
compare the efficiency of different methods and tools.
and use a system that allow you to experiment, and possibly build things on top of JSON data.
then :
welcome to the future!
Top comments (0)