2 ms·
A nice idea, thanks for sharing. I do something similar in emacs with org-capture. I use a capture template that enters a row into a table in an org file. In t
by agentultra 9y ago
A nice idea, thanks for sharing.
I do something similar in emacs with org-capture. I use a capture template that enters a row into a table in an org file. In that file I have some org-babel blocks that computes my histograms and displays a nice graph for me.
Although emacs isn't exactly user friendly for most people. I hope your project gets out there more. It's a useful tool to have.
(As a manager of an software development team my job is to be distracted and handle them effectively... a tool like this has been invaluable.)
- masukomi 9y agoi'd love to know exactly what graphs you've found to be valuable. I've been finding that many of the things i _thought_ would be valuable to see graphed end up looking more like modern art than useful data (people by hour for example) .
- agentultra 9y agoThere are two I use the most; 1. Histogram of frequency by distraction type [0] 2. Histogram of frequency by distraction type filtered by person [1] [0] This lets me know what is distracting me the most. If I find a particular type is a clear leader in frequency then it prompts me to find a way to reduce that particular type of distraction. [1] When I'm investigating [0] if the type is not descriptive of the cause I look to this graph to determine the person who causes it the most. For example the "codehelp" type tends to be pretty strong over all. When we launch a new feature or introduce a new software component on the back end I tend to see a spike in these coming from the junior members on the team who need extra guidance understanding the feature or technology. However when it starts to move away from the average by looking at [0] I'll sometimes look through each person using [1] until I find that there are one or two team members that need extra guidance.... then in a week or two I usually see [0] return to "average."