21–30 of 64 posts
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: 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…
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: 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…
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: 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…
This is why I and most of my team work from home on Fridays (we never book meetings either). It's tempting to dismiss working from home as a way of skipping on work, but there's no other time I can get 4+ contiguous hours in front of my computer with no interruptions or meetings. It's probably my most productive dev time all week, largely because I can plan for it. I frequently and vocally encourage work from home on…
The 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…
She was paid $36MM in 2015 and raised the market cap of Yahoo! by 151% in four years. Some of that compensation is based on success at Google, some of it may be based on her success at Yahoo!, but some of it is absolutely based on her brand. Her brand, in my own mind, is highly associated with her dedication to working long hours.
I work long hours but I'm conscious of a few things: I don't celebrate it. I don't plan to proselytize it like Mayer does. Part of those long hours are dedicated to operationalizing time-sinks so that I don't have to do it forever. I don't expect others around me, especially non-founders, to do the same and like you I believe that for them to do so would likely be a net-negative.
Thanks 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 feed…
Earlier quoted context omitted.
It's literally written by an individual that is male. Let's hope he knows what gender he is.
Then they should have used "How THIS technical co-founder spends HIS time" -- by using "a" instead of "this" he implies a generality.
So while the title could perhaps have been better worded, I can believe no conscious bias was intended.
I work as a freelancer (Europe) and I think I work reasonably hard. But is really difficult for me to honestly log more than 10-15 dev-billable hours during the week. The rest of the time is spent in chat and learning / playing with a new things.
Do your clients understand that playing / trying out new things leads directly to you building the finished product? Or is your playing truly separate from any of your client work?
I work as a freelancer (Europe) and I think I work reasonably hard. But is really difficult for me to honestly log more than 10-15 dev-billable hours during the week. The rest of the time is spent in chat and learning / playing with a new things.
10-15 hours per week is your max? Do your clients understand that playing / trying out new things leads directly to you building the finished product? Or is your playing truly separate from any of your client work?
For living I build e-commerce solutions and backend stuff. And in free time I play more with a frontend. Recently with react/redux and in the long run with every possible new technology on the horizon. I guess I waste a lot of time doing this as most of these things isn't immediately related to client work. ( but over time It helps me to sell to them a few ideas for improvements )
Also, I track my time and habits in detail ( using rescuetime ). Probably without such careful loging I would overestimate how much time I am spending on actual coding.