How a Technical Co-Founder Spends His Time
1–10 of 64 posts
Re: How a Technical Co-Founder Spends His Time
#2It's interesting to note that the meetings time decreased as the management time increased, because often the two are strongly correlated.
In my experience meetings and management time grow proportionally, since meetings are a good way to talk with the team, set expectations and review the results. Or, in other words, some meetings == management.
Re: How a Technical Co-Founder Spends His Time
#3Interesting article, pretty remarkable to be that committed to the time tracking -- I can barely stick with using the pomodoro technique for longer than a few days in a row...
I hope OP continues to grow the dataset. Will be interested in a follow up later on!
Re: How a Technical Co-Founder Spends His Time
#4Interesting article, pretty remarkable to be that committed to the time tracking -- I can barely stick with using the pomodoro technique for longer than a few days in a row... I hope OP continues to grow the dataset. Will be interested in a follow up later on!
According to the HN front page, it takes 60 days for most people to form a habit.
Re: How a Technical Co-Founder Spends His Time
#5It's interesting to note that the meetings time decreased as the management time increased, because often the two are strongly correlated. In my experience meetings and management time grow proportionally, since meetings are a good way to talk with the team, set expectations and review the results. Or, in other words, some meetings == management.
"The meetings will continue until moral improves."
Re: How a Technical Co-Founder Spends His Time
#6The notion that a 130h work week is admirable, desirable, sustainable or useful is ridiculous and should be criticised every time it's raised.
Unless you're working for yourself or working in a job where your contract compensates you by the hour then investing such huge swathes of time I think is destructive.
There is a reason workers united, fought and were martyred for the 8 hour work week and the creeping clawback by industry is a problem.
That aside, very interesting to see such a consistent time keeping record.
Re: How a Technical Co-Founder Spends His Time
#7Off-topic: I really like Overleaf. It removes the barrier of installing all of the compiler, editor and dependencies and allows anyone to jump right in and and start typing manuscripts. That's why I always recommend Overleaf to anybody looking to learn Latex initially.
Re: How a Technical Co-Founder Spends His Time
#8The notion that a 130h work week is admirable, desirable, sustainable or useful is ridiculous and should be criticised every time it's raised. Unless you're working for yourself or working in a job where your contract compensates you by the hour then investing such huge swathes of time I think is destructive. There is a reason workers united, fought and were martyred for the 8 hour work week and the creeping clawback…
An 8 hour work week is definitely something I can get behind.
Re: How a Technical Co-Founder Spends His Time
#9Thanks for sharing this. Is the metime code publicly available? I'm the CTO of another small tech company (https://sourcegraph.com) and I'm also a bit obsessive about time tracking.
I wrote a small open-source CLI that gives you a CPU-profile-like view of time spent on your computer: https://github.com/sourcegraph/thyme. Thought I'd share since OP and others here might find it useful, and I'd love to hear any feedback.
Re: How a Technical Co-Founder Spends His Time
#10> My app had some simple charting built in but no real analysis. It’s only now, six months later, that I’ve had a chance to really get into the dataset
I'm interested to find out if the data influenced the OP from week to week (month-to-month) during the collection phase? Did it influence his keeping up his development by shifting it to weekends? Or was there other catalysts to that? What were they? Were there planned development milestones? were they sized?
Fascinating article.