3 ms·
I've developed two habits that work well for me: 1. Taking walks during the day. I have figured out a lot of tricky design and even debugging questions by taki
by tikhonj 2y ago
I've developed two habits that work well for me:
1. Taking walks during the day. I have figured out a lot of tricky design and even debugging questions by taking a walk. And even if I don't think about programming directly, it still clears my head. Splitting my day up with an hour (or longer) walk leaves me more effective than spending the same time in front of my computer. I usually work remotely, so often this involves walking to a cafe, doing some work there and walking back.
2. Taking walking meetings. I've found this works well for 1:1s, and it works reasonably well for large calls where I don't need to participate much. There are lots of meetings where it's too awkward or doesn't work at all, but converting even a small fraction of my meetings to walking meetings is a real improvement.
Of course, both of these assume a flexible culture where this does not make me look like a slacker and where I can take meetings in different ways. But I figure that's a minimum for having a healthy and productive work environment regardless!
- aeternum 2y agoThe videocall obsession has got to stop for #2 to work. It used to be much easier to do walking meetings and walking calls, now every external call has to be on video and even internal calls there are plenty of people that subtly guilt you or assume you're not actually working if you have video off. I'm about to start leaving video on with the phone in my pocket as I walk.
- tikhonj 2y agoYeah, I've been lucky to work on teams where people are pretty flexible about having video on or off. And for 1:1s walking meetings can work well in person too :)