4 ms·
Yeah, my answer to this is "I don't". If you're even a little bright (which is the most I, personally, can claim) and capable of actually Getting Shit Done whe
by corrral 4y ago
Yeah, my answer to this is "I don't".
If you're even a little bright (which is the most I, personally, can claim) and capable of actually Getting Shit Done when you are working (so, you do, in fact, know your shit, and have decent sense/taste for where to apply effort), surprisingly few hours a week are needed to maintain or even exceed par, lots of places.
[EDIT] Though I guess my main technique for ensuring fully-actually-working time is effective is that I'm fairly serious about tightening feedback loops. This is basically like doing your mise en place when cooking. Make sure as much working time as possible is actually working, and that you can do a write-build-test cycle as fast as possible, make it easy to hop in and do five minutes of work and truly accomplish something, et c.
- sudden_dystopia 4y agoCan confirm, this approach works outside of tech as well. Not just buckling down to get shit done, but be proactive enough to anticipate what’s coming and when so you don’t get buried. Don’t let your in box fill up, look available on IM, answer the phone when it rings, streamline your processes. And then otherwise take the rest of the day off except for anything new that may pop up that you can knock out.