Ask HN: What do you like to do while you wait? When you're waiting for a Zoom meeting, something to compile, etc., what do you like to do to pass the time? My habit is to open monkeytype.com and get one or two rounds of typing practice in. Would love to see if anyone has any other quick productive (or not) activities to do in those passing minutes. |
So I guess I like to read your posts while I wait <3
Alternatively, for learning languages I really like Lingodeer, Busuu, and Clozemaster.
You might also be interested in: https://news.ycombinator.com/item?id=32430406
It is helpful to apply the kanban principle and have exactly one task you do while waiting so you don’t waste time switching between tasks.
Later, when i back home, i usually convert this notes into OpenStreetMap contribution. It also could serve as my own writing prompt or something.
I’m trying to get better at reading a book.
I don't think it's healthy to need constant activity/distraction. It's an addiction IMO. So if I'm standing in a checkout line or waiting a few minutes for a zoom meeting, I do nothing.
But what is this thing called "waiting for a zoom meeting"? That does not really exist for me.
I was probably actually doing something and so I just keep doing that until the exact time that the meeting starts. If the meeting is at 9:30, I try to join at exactly 9:30 or when I do something else where I might be too much in the zone and miss the meeting, I might join early and just have camera and mic off. And once someone joins I'll switch to small talk.
Waiting for something to compile should also usually not exist, as in the compile times are either so short, that it makes no sense to do anything but "rest the mind for 5 seconds" or they're so long that I just try to schedule them in a way where they don't make me wait. E.g. I like to use our CI system to tell me about any tests that I might have broken that were not apparent from the files I was changing directly, because running them locally makes my computer slow enough that doing something else gets frustrating. So I just commit and push and in the ~10 minutes that takes I might create the PR already, double check that the diff looks like what I expected and make any adjustments necessary. E.g. sometimes I see that I forgot to undo some hard coded value I put somewhere in the code as a shortcut while testing in my dev env, any variables that are still called `blah` etc.
If this sounds too much like concentrating on work and only work during work hours. Yes, that's what I do. When I work, I'm 100% work, 0% watching Youtube and such (unless it's some conference talk recording or something I guess :) - that counts under the 'training budget'). I don't even answer personal emails during work.
Guess what I don't do during non-work hours? Work! When I shut my computer down at whatever time that is, work is dead to me. I don't have slack on my phone, I don't have work emails on the phone and none of that can send me any notifications. If you really need to reach me for an emergency, my phone number is available but you better only call me in actual emergencies, as in the on-call people can't figure something out, production is burning and we're loosing money by the minute and I wrote the code. Times at which I expect not to want to work have an Out of Office on my calendar. Like lunch time, morning hours I don't want meetings in from other timezones, afternoon hours at which I don't want any meetings which might then run late even if I'm actually still working during that time normally. And OoO I find is great because I don't actually actively say "No" to someone that might easily start arguing because they feel offended I told them no. It's just an automated message from my OoO.