ejmg
commented
6 years ago this sounds really nice.
that said, i need to look into the efficiency of tracking as simply a json vs a minimal dbs (that isn't just a glorified json) given the number of tracking features we are embracing.
Do you have any input on this? So far I have roadmapped:
- tracking per day #15
- tracking by topic/todo item #38
- exportability of said tracking #38
- time wasted/procrastinated/lapsed #60
- velocity (this issue)
- ????
I do not know the performance measurements in terms of overhead and memory for json serialization as compared to, say, sql-lite. preferably, we would use something even more stripped down than sql-lite.
This is going to be such a fleshed out feature that I'm giving it its own tag either way.
We use this at work to track how many points a team is able to complete in a single sprint. It's literally just the average. It would be nice to be able to track, on average, how many pomodoros a user is able to get done in a day or week. This would also be nice for long term stats tracking, i.e., productivity over a week, month, semester, quarter, etc.