In the 5 seconds of thinking what I'd wish I'd seen before I clicked the link:
Pre MVP: 80% dev, 20% biz dev
Pre Revenue: 20% dev, 80% biz dev
Pre Profit: 80% hiring, 20% dev
Profitable: 100% biz dev
How a Technical Co-Founder Spends His Time
11–20 of 64 posts
Re: How a Technical Co-Founder Spends His Time
#12The 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.
Then you'll love my ebook "1 step to working 8 hours a week and get paid $62,262/hr by Google. Number 1 is a doozy!"
Re: How a Technical Co-Founder Spends His Time
#13It'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."
AKA the project productivity death spiral
Re: How a Technical Co-Founder Spends His Time
#14Earlier quoted context omitted.
An 8 hour work week is definitely something I can get behind.
Then you'll love my ebook "1 step to working 8 hours a week and get paid $62,262/hr by Google. Number 1 is a doozy!"
Then you'll love my ebook "1 step to working 8 hours a week and get paid $62,263/hr writing ebooks!"
Re: How a Technical Co-Founder Spends His Time
#15*Or her time.
Re: How a Technical Co-Founder Spends His Time
#16The 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:
I can have days where I do a million small things and hop quickly from task to task.
Or, I can have days where I work on big issues and should not be interrupted by small issues.
But, if I think I'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.
Re: How a Technical Co-Founder Spends His Time
#17*Or her time.
It's literally written by an individual that is male. Let's hope he knows what gender he is.
Re: How a Technical Co-Founder Spends His Time
#18*Or her time.
Nope. Title refers to the author himself.
Re: How a Technical Co-Founder Spends His Time
#19The 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: I can have days where I do a million small things and hop quickly from task to task. Or, I can have days where I work on big issues and should not be interrupted by small issues. But, if I think I'm going to have a day where I work on a big thing and it turns out I get interrupt…
> But, if I think I'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
These can be some of the most frustrating and dispiriting days
Re: How a Technical Co-Founder Spends His Time
#20In the 5 seconds of thinking what I'd wish I'd seen before I clicked the link: Pre MVP: 80% dev, 20% biz dev Pre Revenue: 20% dev, 80% biz dev Pre Profit: 80% hiring, 20% dev Profitable: 100% biz dev
Interesting. Would love to hear more about your thoughts around this.