<story><title>How a Technical Co-Founder Spends His Time</title><url>http://jdlm.info/articles/2016/07/04/cto-time-minute-by-minute.html</url></story><parent_chain></parent_chain><comment><author>bluetwo</author><text>The biggest thing I learned when analyzing my time, which I wish I had recognized earlier, was that I can have two types of productive days:&lt;p&gt;I can have days where I do a million small things and hop quickly from task to task.&lt;p&gt;Or, I can have days where I work on big issues and should not be interrupted by small issues.&lt;p&gt;But, if I &lt;i&gt;think&lt;/i&gt; I&amp;#x27;m going to have a day where I work on a big thing and it turns out I get interrupted by a million little things, I end up doing nothing well and end up very unproductive.</text></comment>
<story><title>How a Technical Co-Founder Spends His Time</title><url>http://jdlm.info/articles/2016/07/04/cto-time-minute-by-minute.html</url></story><parent_chain></parent_chain><comment><author>beliu</author><text>Thanks for sharing this. Is the metime code publicly available? I&amp;#x27;m the CTO of another small tech company (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;sourcegraph.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;sourcegraph.com&lt;/a&gt;) and I&amp;#x27;m also a bit obsessive about time tracking.&lt;p&gt;I wrote a small open-source CLI that gives you a CPU-profile-like view of time spent on your computer: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sourcegraph&amp;#x2F;thyme&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;sourcegraph&amp;#x2F;thyme&lt;/a&gt;. Thought I&amp;#x27;d share since OP and others here might find it useful, and I&amp;#x27;d love to hear any feedback.</text></comment>