Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham thank you for making PuTTY. Been using it for over 20 years
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham Keep a printout of “Buridan’s Principle” on your desk and read a few paragraphs until you can resolve the dilemma.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham I've sadly had to delete the bookmarks and history entries for your puzzle collection because that was always something I'd pull up when I was "microbored" without even thinking, and now that's 2–5 minutes wasted.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham That's when you pick a few tomatoes on Animal Crossing and suddenly it's three hours later and the task has long since completed
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham That''s why regular ovens take less (of my) time than microwaves. Of course microwaves finish sooner, but once I put something in the oven I go away and do something else. The oven is not taking my time. But if I stick a microwave dinner in to cook I'm standing there watching a two and a half minute timer count down before I peel back the film lid stir and put it back on for another two and a half minutes. The 25 minutes it takes for the oven to do it's business can be spent productively. However if I'm standing by a microwave all I can to is get my phone out and read your wonderful toots. Hmmm maybe that's not so bad.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham 10-20 seconds is the perfect length of time to write a microblog about microboredom
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham it's like in drivers there's some threshold where it's just not worth waiting for an interrupt but polling feels wrong.
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham
You're patient. By the 20 second mark, I'm in the kitchen.(Used to be "reading slashdot", but I believe that has turned into one of those fake comparison sites a'la alternative.to).
-
Followups from my previous post inspired me to invent the word 'microbored': the level of boredom that happens when something is right on the threshold where you look for something else to do.
For example, if I'm waiting for a compile that takes 1 second, I'll just sit for a second until it's done; if it takes 5 minutes or more then I _obviously_ need to find something to do while I wait (go make a coffee, open up a blog post, check Mastodon, whatever). But somewhere in between, at maybe the 10–20 second mark, it's a dilemma: sitting for 20 seconds doing nothing is a bit annoying, but anything I start doing in those 20 seconds won't be finished when I need to get back to looking at the results of the compile, and maybe the mental context switch costs more than it saves.
That's microboredom. It's not _too_ unpleasant in itself (there are much worse forms of boredom). But it's a more insidious waste of your time than a 5-minute delay, _because_ there's no way to spend the time more usefully or pleasantly.
@simontatham Isn't that what your puzzle collection is for? I think 20s is about right to finish Galaxies on the standard settings ...
-
R relay@relay.an.exchange shared this topic
