If you live in one of the temperate zones on Earth, you’ve probably been beset by mosquitoes at some point. Outside the tropics, where malaria and numerous other diseases are a scourge, mosquitoes are (thankfully) mostly an annoyance.
Somewhere in human evolution, the above was (presumably) an evolutionary advantage. Perhaps it’s actually because snakes are rarer than mosquitoes, and it is more possible to avoid them. Perhaps it’s because the defense against snakes and mosquitoes is different. For snakes, avoiding them or fighting them off might be the best survival tactic, as each individual snake could kill you. For mosquitoes, the ‘go away’ reaction to annoyance is perhaps actually the best defense, as we automatically wave our hands to shoo them away.
Interestingly, if you think about it, we find mosquitoes annoying, but mosquitoes didn’t evolve to be annoying, we evolved to be annoyed by mosquitoes[1]. The buzzing about, the whine of their wings, cause automatic reactions from our auditory to our reflex systems.
But what about swatting? I know that I almost automatically swat at mosquitoes, either to grab them out of the air, or swat them when they’re trying to drink my blood….but I don’t know if that’s an actual evolved automatic response, or something learned.
What is your reaction to mosquitoes? What are your other (possibly adaptive) phobias and automatic reactions?
[1] Whether we evolved from being scared to being annoyed, or from ignoring them/thinking of them as food to being annoyed is anyone’s guess….or perhaps more accurately, someone else’s research.
The utopia of Star Trek. Teams of people working together to solve problems, living in a post-scarcity society, focused on science and exploration.
This is sometimes called ‘Fully Automated Luxury Communism’ (from the Atlantic article), sometimes called ‘Fully Automated Luxury Gay Space Communism'[1] (by the memes).
One would think that if this was truly our goal as a species, we would be working together, working tirelessly to get ourselves closer to this post-scarcity utopia. But we aren’t. Something is getting in the way (probably many somethings). Here is my (tentative)[2] list of obstacles, each to be explored in a subsequent post (linked from here when I’m done):
My list of possible Reasons Why We Can’t Have Nice Things:
1) Humans just don’t want nice things. Either because they’re uncomfortable with the required introspection or amount of change required, or because it interferes with or would reduce something they want instead (cf. ‘finite games vs. infinite games'[3])
2) The Ideology of Conservatism. Much of conservative ideology is built around unnecessary hierarchies and the presumption that humanity is better off when more people are worrying about the lower levels of Maslow’s Hierarchy.
3) Capitalism. Somewhat related to the above, the goals of capital in most of its incarnations are at odds with post-scarcity, and it tends to shy away from incarnations that could be congruent with it, often as a result of:
4) Regulatory Capture. Any system that would lead to post-scarcity must have some boundaries or regulation. Unfortunately, any such regulations are enforced by humans, and humans are subject to ‘capture’ by those they are meant to regulate (cf. The Big Short)
5) The inability/unwillingness of humans to scale delegation or decision-making. Caleb Gamman mentioned that Film Studio execs attempt to concentrate power and film ‘IP’, but are unable to flexibly use all of the resources (of various types) that they have concentrated, being only able to focus on a small number of things at once, leaving large amounts of resources to languish or be inefficiently used.
6) Others to be named later
Let me know what you think! What did I leave out? What did I get wrong? Should we be aiming for something different as a species?
[1] This phrase feels surprisingly difficult, probably due to the ‘Green Great Dragon‘ problem
[2] Tentative for now, as I write the other posts that make up this series. This list may change, the ordering may change.
[3] In this context, I’m referring to the difference between a ‘finite game’, one which is played to gain power or ‘win’ against other humans, and an ‘infinite game’, which is played for the betterment of one’s self. I was introduced to this concept by the title of the book:’Finite and infinite games’ by James P. Carse, which purportedly plays with some of these concepts.
[Note that this post may include mild spoilers for the Gold Box games ‘Pool of Radiance’ and ‘Curse of the Azure Bonds’, as well as ‘TES IV: Oblivion’.]
How ‘large’ is a game? How many ‘encounters’ does it have? How many ‘quests’? (And how does the type of encounters & quests affect how large the game feels?)
In an attempt to quantify my feelings, I’m working on ways to measure the ‘size’ of games, and it’s become clear that we need some standard definitions.
Most Computer Role-Playing Games (CRPGs) have the concept of ‘encounters’ and ‘quests’.
‘Encounters’ are generally defined ‘this is who you meet/this is what happens when you go to this place’.
‘Quests’ are generally defined as ‘Someone asks you to go somewhere and do something’.
Encounters are simpler, so we’ll investigate them first.
Many aspects of these definitions are cribbed from the pen and paper language around RPGs, where there will be a map with a numbered encounter key, describing what happens in each location. This visual language has persisted in ‘clue books’ and online hint/walkthroughs, such as this one, from the clue book of one of my favourite CRPGs, ‘Pool of Radiance’:
In the picture above, you can see 5 numbered encounters, with some of them happening or being able to happen in multiple locations.
In this particular instance, encounter ‘1’ is an encounter with some Kobolds who are trying to sneak away from you, with a chance of occurring each time you enter one of those squares. Encounter ‘2’ is a large multi-wave battle that starts whenever you enter one of those locations (triggering an ambush).
Other similar encounter keys might have a ‘each time you enter one of these locations for the first time, ‘.
So, how do you count the number of ‘encounters’?
Let’s break down the definition of ‘encounter’:
– You go to a place[1]
– You see something/meet someone/meet something
Encounter ‘1’ above triggers when you enter the first place out of a logical set of places that you enter, that probably feels like one encounter for these purposes, as it’s happening in a logical place.
Encounter ‘2’ is similar.
At the opposite end are ‘random encounters’, which are generally used to use up player resources, or to create a sense of urgency, so that players don’t dawdle[2]. These I will generally count, but count separately from ‘placed’ encounters. (Edit: S mentions that random encounters, for example in Pokemon games are often used by the player to ‘grind’ or ‘farm’ XP, to level up their characters outside of the more story-based game content. Interestingly, one could measure how much a game is in the ‘survival horror’ genre by how difficult and resource-consuming random encounters are (cf. SystemShock).)
Somewhere are in the middle are random encounters which have a sequence of some sort, but are not tied to any one particular location, such as those in the ‘random’ dungeons in Curse of the Azure bonds:
Game locations designed in this way have the same ‘number’ of encounters, and even though they occur in a defined order, telling a story, the fact that they happen entirely at random, without regard for the location or geography, breaks immersion terribly (at least for me). They tend to feel emptier than other encounters, and (to me), only contribute a fractional amount.
What if a place is different when you go back? Is that a second encounter? I don’t know yet. I’ll have to assess that when I get to examples.
What if you have the same encounter 10 times, with each in an identical but seemingly logical place(such as guard posts)? Is that really 10 encounters? Not really…but it also doesn’t really feel like only one. I posit that it’s somewhere between. I’ve been using a log function internally, probably with base e, as base 10 feels too large and base 2 feels too small, but I could easily see it be something else, where the first few seem ‘real’, but after that they run together much more.
Now, let’s move on to ‘quests’
We can break ‘quests’ down into:
– Someone asks you to do something
– You go somewhere
– You do a thing
Pretty simple, right? This includes all ‘fedex’ fetch quests, escort quests, and even most of the ‘escape from this location’ quests.
The trick is when one of the above is missing, such as when you accidentally find the object of a quest before someone tells you to go looking for it (VLDL has a humorous portrayal of this here). This is generally still defined as the same ‘quest’ in the game notes, as well as in strategy guides, but some (such as S) believe that the ask is required (and without the ask, this is simply ‘world-building’).
Sometimes, no one asks you to do something, but there is still a reward when you do it (such as this quest from Oblivion[3]), or they are happy that you’ve done it (such as the dungeon below Kuto’s Well above, where you get a quest reward for defeating the bandit horde of the notorious Norris the Gray). I would still call those ‘quests’, though. Perhaps there’s a difference between ‘Quests’, which require all three, and ‘quests’, which are ‘whatever the game designer says’. 😀
What if you don’t need to go somewhere? This might just be an encounter, or if it’s particularly involved, it could be an all talking interpersonal drama gaming session (or even a game within a game….)
What if the ‘thing you need to do’ is just getting to the destination? I feel like this one can go either way. Most of the quests in the Oblivion Assassins’ guild have a ‘pre-quest’ which involves getting the assignment. I’m not sure why they did it this way, but it kind of makes sense that an assassins’ guild would want it to be difficult enough to figure out what they were doing, that it might be a quest just to get to the dead drop to find the assignment. However, about half of the locations in Curse of the Azure Bonds are just places that the party has to traverse to get somewhere in order to do something important. To me, this doesn’t really feel like a separate quest (sometimes not even like a separate location), and in a lot of ways makes the game feel smaller.
What do you think? How would you define an ‘encounter’ or a ‘quest’? Do you disagree with any of my definitions above? Let me know in the comments below!
[1] There are variants where encounters can come to you, but that’s usually a different type of story/measurement and is out of scope. This method would probably treat these as one encounter, or you could get really fine-grained and treat that as an entire adventure with ‘locations’ represented by the state of affairs at each step.
[2] There’s also a theory that random encounters are useful because they allow for a differential in stakes between different encounters by having lower-stakes encounters.
[3] I can’t begin to describe how frustrating this quest was, and how difficult it was to do, even with the walkthrough page open beside me. Probably the most ‘realistic’ of the ‘finding something hidden’ quests out there, though.
Spock is the center[1] of Star Trek. Many othershave written (or videoed) about this, either about Spock himself (and Leonard Nimoy’s excellent portrayal), or the ‘part-human’ outsider archetype that has been present in every Star Trek show/movie.
Perhaps my favourite Spock scene (or at least the one that I find myself quoting most regularly) is this one from Star Trek IV: The Voyage Home. Shortly after having his katra rejoined with his body, Spock is working through a set of tests of memory and problem solving across numerous disciplines, when, after successfully navigating through and solving myriad technical problems three at a time, he is blocked and stumped by the simple and very ‘human'[2] question: “How do you feel?”
I suspect that many other neurodivergent folks also saw a lot of themselves in Spock. Whether it was aspirational (such as his ability to quickly solve problems across disparate disciplines very quickly in critical situations), or because we connected with his ‘outsider’ nature (his slow learning to be more in touch with his human side, or Data’s yearning to be more human), or even because we also wanted to be part of a tightly-knit team, where the science officer would figure out part of the problem, and pass it off to the leader, who would assemble it into action and a solution.
Much of this blog has been about chronicling my journey to better understand myself, from my first post on paying more attention to and bringing out fleeting thoughts, to my entire category ‘Thoughts on Thoughts‘. Through all of this, I continue to search to understand how I feel and why I feel the way I do. In a way, I think[3] that working to understand how one feels is fundamental to the human condition, and we do ourselves a disservice by not investing in investigating ourselves in this way.
There are fundamental questions humans have been asking ourselves since time immemorial: ‘Why are we here?’ and ‘What is our purpose?’. Perhaps a lot of the answers boil down to ‘How do you feel?’
[1] Many of the meanings of ‘center’ are applicable here, whether it’s the logical ‘heart’, or the ‘focus’, the self-insert for an otherwise under-served audience, or even the person or archetype that many plots revolve around, whether it’s solving problems or being put in peril.
[2] This is part of Amanda Grayson (Spock’s mother)’s work to help Spock reattach his human side, now that his katra has been reattached ‘in the Vulcan way.
You can also see Spock’s answer to the question at the end of the movie, showing that he now better understands friendship and himself (source for this insight):
“Oh, that’s a fun failure mode!” I was talking with a friend of mine recently, and they were talking about a technical problem they were solving[1], specifically about the failure mode that they had seen, and before they could explain their solution, I made the exclamation above.
Failure modes have always fascinated me. I don’t know if that’s a cause of or a result of[2] me going to engineering school[3]. I remember being fascinated (and appalled) by the video and story of ‘Galloping Gertie‘. The torsional twist as a reaction to wind and subsequent failure mode[4] is an image I’ll never forget.
Our undergrad bridge-building course professor[5] seemed to also be very interested in giving us images and experiences of materials actually failing. My favourite was his demontration of the failure characteristics of steel cable. In class, he showed us a diagram similar to this one:
Notable parts of this stress-strain diagram include but are not limited to:
– The ‘elastic region’, amounts of stress/force/pressure where the material will stretch but return to its original shape and size[6]
– The ‘strain hardening region’, where the material will adjust and become somewhat stronger. (This may be undesirable)
– The ‘necking region’, where the metal/material starts to lose strength because the atoms can no longer fill in the gaps, causing narrowing of the cross-section (the ‘necking’), eventually leading to fracture, where the material fails
The demonstration included measurements of the deformation of the steel, using a precise length measuring device[7] to provide numerical measurements. Such a device is required, because the deformations we’re talking about are tiny, due to the large Young’s Modulus of steel.
Another demonstration was using a jug of water to break a wooden dowel. The dowel was fixed to a desk, with one end extending (cantilever-style), where the jug was hung at various points. This was intended to show how the torque[8] (of the mass of the hanging water times the distance from the cantilever point) would increase the force, leading to eventual failure of the dowel.
At least that was the intended demonstration. The dowel was so flexible that it bent downwards far enough to minimize the amount of torque/force, preventing it from breaking. So instead, we got to see a failure mode of the intended failure mode instead (and learned something about the resilience of trees!).
Perhaps most memorable was witnessing a failure mode of the professor, who, discontented with his dowel not failing in the experiment, broke it himself over his knee, showing us both the actual failure mode of wooden dowels and how frustration and anger can contribute to engineering failures.
For a great explanation of the different failure modes of different types of materials, especially what it is that makes wood so resilient, I recommend the textbook we used in this course:
Both of these demonstrations left strong impressions on me. I still remember them more than 25 years later (and I suspect many of my classmates do as well).
Given how visceral and effective these demonstrations were, it would make sense to work out a (reasonably) full set of reasons that engineering[9] projects fail, and create demonstrations and labs based on those, so that the students have those visceral memories to call upon, to warn and inform them.
But what is that set of reasons that engineering projects fail? How do you categorize and teach failure modes systematically?
That’s a question for next time! (Spoiler alert, it will probably involve the ‘swiss-cheese model‘.)
[1] It was a type of problem that I had designed a system to avoid in the past, so it was kind of cool to see an instance of it ‘in the wild’, so to speak.
[2] Or both!
[3] Or growing up with a parent as an engineer
[4] And the poor dog!
[5] Thanks, Prof. Collins!
[6] For those who have been following the news recently, this is one of the reasons that steel is used for pressure vessels such as submarines.
[7] I was originally going to suggest that this was some sort of strain gauge, but if my memory serves me correctly, I remember a dial moving showing deformation. If anyone knows the type of device typically used for such a test, please comment below!
[8] This may have also been the lesson where I learned the second meaning of the phrase ‘Every Couple has its moment‘.
[9] I’m using the word ‘engineering’ here because all of the demos I talked about were related to mechanical engineering/bridge building, but much of this will apply to software engineering as well.
Links to image on Wikimedia Commons, Creative Commons license available there: Stress/strain curve
S’s note to me, to help me write this post: “Please pick two failure modes and write about them! Then you can add a bonus failure mode, which was you getting overwhelmed by the number of possible failure modes and timing out before writing anything. “
So, I was out for my morning walk today, and it started to rain. Luckily, I had planned ahead and brought my umbrella. I opened it up, and was standing there, enjoying the rain…and then I started to walk, and my legs started to get wet. I stopped, my legs stopped getting wet, I started walking, my legs got wet again.
The question is why?
I narrowed the problem down to the following variables:
– Height of the person (technically, the height of the edge of the umbrella)
– Walking speed and wind speed (I’m putting these together for reasons you’ll see later)
– Size and shape of rain droplets (this is to measure terminal velocity)
– S also added ‘size of umbrella’, but I’ll address that in the assumptions section
This is a lot of variables, so let’s make some assumptions:
– The human in question is about 2m tall (accurate within 5%)
– The edge of the umbrella is about 2m from the ground (accurate within 10-15%)
– The edge of the umbrella is about 25-50cm from the front of the leg horizontally
– We count the leg as getting wet as when the rain hits the front of the leg just above the ground
– Length of a step is about 80cm (as per this page)
– Raindrop terminal velocity is about 20m/s, as per this graph:
– Wind-speed is negligible, as per this chart from Environment Canada, showing that wind at the time in question (9am) was about 2km/h, from the North:
Now on to the math!
We can easily show that with negligible wind, rain falling straight down will not hit the legs.
But assuming 90-degrees from ground vertical legs, what wind-speed would be necessary to rain on them?
At 20m/s, the rain would need to travel 0.25m or 0.5m horizontally as it traveled 2m vertically, or a horizontal wind of about 20m/s * 0.25m/2m = 2.5m/s or 9km/h for 25cm of umbrella overhang to 18km/h for 50cm of umbrella overhang.
So it turns out that the wind-speed was actually really important, as you can see that at other points today, it alone would have made the difference.
Now, what happens when we start walking? There are two factors at play here:
– Walking speed
– Extension of the leg forward out of the protection of the umbrella as you take a step
So we have to add some more assumptions:
– Assuming an average walking speed of about 5.4km/h or 1.5m/s
– Assuming that the toe to toe per step distance is 0.8m (from above), assume that at maximum extension, the tip of the leg is 40cm ahead of the body
Using the wind-speed calculation above, we can see that 1.5m/s of forward motion would only counteract about 1.5m/s / 20m/s * 2m = 15cm of umbrella cover, not enough to make your legs wet.
However, if your leg is 40cm ahead of your body, that would be enough if your umbrella was any reasonable amount off ‘exactly centered’ over the front of your body, and if your leg is 40cm ahead, and your walking speed adds another 15cm, that is enough to counteract even perfect vertical umbrella placement (40cm + 15cm > 50cm).
My experience this morning suggests that either the rain was falling more slowly than 20m/s, I was walking slightly faster than 1.5m/s, or I was resting the umbrella diagonally over my shoulder (most likely). This would have given me the approx. 25cm protection above, and caused my legs to be wet only while I was walking.
How would you calculate this? What would your assumptions be? Have you experienced this? Are you going to test this the next time it rains? Are you as surprised as I am that leg placement and step length are much more important than walking speed (as long as you’re only walking)?
Recently, a couple of friends of mine shared the following meme:
On the face of it, it may seem harmless, poking some fun at people who not only know less than you, but who know less than you consider reasonable (or perhaps even ‘possible’!)[1].
However, this laughing at others can lead to contempt, and a reluctance in the willingness of others to ask questions, due to the loss of psychological safety.
So, why might people laugh at those who know less about a topic than they?
Some describe surprise as a necessary component of laughter. You can be surprised that others know not just less than you know, but even less than you think is possible to know. This cognitive bias causing this surprise is a subset of the ‘Curse of Knowledge‘, perhaps best summed up by this drawing from Rajesh Mathur:
Sometimes, however, the laughter is not just about surprise, but also comes from a place of insecurity, the desire (conscious or not) to place one’s self above others. This could also be a trauma response, perhaps to experiences with ‘Sealioning‘, where people will repeatedly throw bad-faith questions into a debate or forum instead of engaging with the argument directly.
Another variant of this occurs often in teachers (and oddly enough, IT professionals), where if you’re continually hearing the same question from many different people, it can feel like ‘they just don’t learn'[2], because each year (or semester or day), you get a new person who hasn’t asked that question yet.
So, why might people be asking questions like this?
– They genuinely don’t know: As shown in the diagram above, the variability in knowledge between humans is vast. Even though you know about Oppenheimer because you’ve read multiple books on the subject[3], others might only have a passing knowledge, or even none, despite his pivotal involvement with the start of the Atomic Age.
– They might be mostly sure, but their experience with the thing made them doubt, or they heard a rumor….and the consequence[4] of their assumption being wrong is so large, the ‘importance x likelihood'[5] equation pushes them to ask the question, humans being loss-averse.
– They’re asking a slightly different question: ‘Is Oppenheimer based on a true story’ could mean a lot of different things. There’s a wide range between how much the movie ‘300‘[6] is based on a true story and how much ‘Oppenheimer‘ is. The question could easily be a rephrasing of “how close is the movie ‘Oppenheimer’ to a ‘true story’?”
– They may have difficulties expressing the specific question they want answered: I think it’s worth mentioning that the ability to ask specific targeted questions into a search engine is a (mostly learned) skill, and like all skills, is subject to privilege and ableist gatekeeping. In fact, one could argue that a large part of the uptake of GPT-like software is their ability to answer peoples’ questions when they are not phrased precisely, helping those who are less able to quickly articulate precise thoughts in written form.
– The search engine could be condensing or de-duplicating the wording of questions asked: On a purely technical note, the search engine has a limited amount of space on the page, and it would make sense that they would condense similar questions into perhaps the simplest and clearest version, making it look like people were very commonly asking a simple question.
Thanks for joining me on this wandering journey. I want to learn (and help others learn) to treat others with more kindness, and it’s important to me to deconstruct all of the reasons behind why I (or others) might be doing this. Thanks for reading!
[1] Having done a bunch of teaching, I was aware of the importance of teaching to different styles of learning, and also to different levels of knowledge, but I remember first hearing about this specific subset of this bias relatively recently, probably in a meme, where an expert in a field says ‘how can they not know about this ?’
[3] Most of my knowledge and understanding of Oppenheimer is from Feynman.
[4] This consequence can be social, such as ‘why didn’t you know about this?’, or personal, such as ‘I don’t want to change the way I think about this unless I have to’, amongst others.
[5] Humans are generally bad at judging the overall expected value of ‘Low-Probability, High-Impact’ events, which is probably why insurance is a thing, although the reduction in distraction/open-loops is probably worth it.
[6] Yes, I know ‘300’ is based on a graphic novel, that’s part of the point I’m trying to make. I’m specifically mentioning 300 because of the large number of known historical inaccuracies and general problematic-ness. There’s also a huge conversation about ‘The Western Canon’ that is out of scope.
What if meetings had a ‘hit points bar’, that showed how healthy they are?
Yesterday, S & I were talking about unhealthy & pointless meetings, and S had the following idea:
What if, every time that someone didn’t show up for a meeting[1], that meeting would ‘lose hit points’?
Each meeting has a number of hitpoints, its initial value related to:
– The length of the meeting[2]
– The number of participants
– The ‘importance’ of the meeting organizer or participants[3]
Those hit points change when:
– Each time someone forwards, ‘accepts’, or attends a meeting, the meeting is healed and soothed
– Whenever someone ‘declines’ a meeting, or perhaps worse, no-shows, the meeting is attacked and takes damage
– Whenever someone participates in a meeting, the meeting is bolstered[4]
When hit points decrease below various thresholds:
– The time allocated to the meeting decreases
– The number of people able to attend decreases[5]
– The meeting timeslot moves to a less desirable time[6]
– The meeting becomes less frequent[7]
Note that if any of the above go to zero, the meeting is cancelled
More outlandish ideas
– Meetings can fall asleep (meeting doesn’t happen this week)
– Meetings can be poisoned (meeting loses ‘hit points’ over time)
– Meetings can catch diseases (meeting is at half-length or half bandwidth until ‘healed’), etc…
– People could be given tools or ‘potions’ to heal or harm[8] meetings
– Meetings could be automated and given tools to sort it out amongst themselves, a la ‘Doom as a tool for System Administration’.[9] This logically would lead to:
– Meetings can have ‘classes’ such as ‘tank’ (absorbs damage meant for associated meetings) or ‘healer’ (actively heal associated meetings) or ‘DPS’ (strike back at competing meetings[10]
Some possible wrinkles:
– Some meetings might only ever have a small number attending out of those invited (such as a large Scrum of Scrums), but might be very useful for those who attend, and not a significant distraction for those who do not. We want to retain that usefulness while removing or reducing meetings that don’t have that usefulness…a ‘meeting budget’ [11] might be a way around that
– How does this work with 1:1s? They are generally acknowledged to be vitally important, but how do they fit in? Can one make a personal sacrifice to move ‘hitpoints’ from a 1:1 to a larger meeting when it’s really important?
Closing thoughts, some choice quotes by S:
—S: “Each meeting has a ‘power level’, which determines how many of its attendees it can hold on to….if it loses power, they can peel away & escape?”
—S: “It just occurred to me that the meeting is a monster, not a friend….why is the manager trying to heal the monster?”
[1] (if they weren’t on PTO). Also, when I say ‘meeting’ here, I generally mean ‘meeting series’, as the measurement of the health of a meeting while it is in progress, while very interesting, is a separate topic and out of scope
[2] Longer or larger meetings are not necessarily better, but they might take more effort to completely eliminate, having built up some inertia over time. One could get around this by assigning more ‘hit points’ to the first half hour of a meeting, with progressively fewer per unit of time as it gets longer. Similarly, with the number of attendees; A meeting with 1,000 people might be 500 times more costly than a 1:1, but is it 500 times more important?
[3] The importance of the meeting participants can go either way. If the people who want the meeting are ‘important’, that could be an argument for keeping the meeting. If they show up and don’t participate[4], that could be a clear signal that they should be removed or the meeting is not that important.
[4] Here, ‘participate’ is tricky….If you have a regular meeting where people of ‘importance’ get very useful information by listening, how do you measure that? Scientific talks or status updates between departments might be good examples of this. Also, ‘vigorous participation’ can be difficult to measure, and as ‘engagement’ metrics show, difficult to measure without encouraging loud arguments….One could also use whether video is turned on or not as a sign of engagement, but different organizations may have different cultural norms around this, and there may also be equity issues with this.
This could also lead to meetings being squeezed; When the ‘energy’/’usefulness’ of a meeting (perhaps measured by when people leave or enter) is consistently high all the way through, there is no change….when this decreases for marked sections of the meeting, the meeting ‘health’ decreases until the length of the meeting makes it so that the meeting has a consistently high energy all the way through
[5] IRL, this could be done by reassigning meeting rooms, virtually by restricting the number of simultaneous attendees.
—S: “Each meeting has a ‘power level’, which determines how many of its attendees it can hold on to….if it loses power, they can peel away & escape?”
[7] E.g. from every day to 3 times a week, from once a week to once a month. This is already done in an ad hoc way for many types of meetings, for example when a team decides to go from daily to 3/week ‘standups’.
[8] Being able to harm other meetings feels like a very bad idea, but it might lead to fun stories 10 years later
[10] If you assign classes and automate meetings ‘interacting’ with each other, you might be able to clear your calendar (or everyone else’s calendar) very quickly….Also, we went back and forth about what each ‘class’ each type of meeting might be, for example, depending on the importance of the meeting, or how reliably it is important (regularly somewhat important like a status meeting, or rarely very important like a ‘these are the code changes going out around the organization’ meeting)
[11] A ‘meeting budget’ might make more explicit the opportunity/social capital cost people incur when arranging meetings (and help alleviate the issue of junior folks not wanting to ‘waste the time’ of senior folks to bring up issues early).
I was reading a random post recently, and came across a mention of ‘Wandel durch Handel‘, in the context of whether embargoes or increased trade are more likely to induce political change.
So, this is not a particularly innovative concept, being an obvious special case of the ‘how much do you engage/meet people where they are vs. set boundaries?’ question.[2]
However, in a debate (or other timing-critical or adversarial conversation) context, you could see how there being a specific name for this specific incarnation of this concept, and your opponent being able to wield it, would lend them an advantage, as you are momentarily confused, perhaps unwilling to ask what they mean, or waiting for context so you could respond appropriately[3].
So, how do you deal with this? One common tactic is to basically ignore what the other speaker is saying, and focus on your prepared talking points. This can be useful in many contexts (not just political contexts), but (I think) a much stronger method is to be better read, to do all[4] the research on the topic at hand.
For the specific case of ‘Wandel durch Handel’ (which I just noticed has a rhyme that kind of rolls off the tongue, at least the way I pronounce German), general knowledge on foreign policy, international trade, or even speaking German, would have made a significant difference to being able to react to the concept. With warning, one could do the specific research/briefing mentioned above, before the interaction with the hostile[5] person.
There are of course many elements of privilege/class/etc. involved in this conversation, not the least of which is “You don’t even know ‘X’?!? You must be uneducated!” All I can say is that there are people with different levels of rhetorical ability and expertise (and ‘expertise’) on all topics, and the Internet is a great help to level the playing field.
Happy learning!
[1] “Wandel durch Handel (WdH, German for “Change through trade”), also known as Wandel durch Annäherung, is a term referring to a political and economic notion, mostly associated with German foreign policy, of increasing trade with authoritarian regimes in an effort to induce political change.”
[2] And also an obvious corollary to the concept of embargoes.
[3] You can see how this is somewhat similar to a ‘Gish Gallop‘, where instead of deploying a large number of arguments of questionable strength, one’s opponent merely throws jargon.
[4] I don’t exaggerate *that* much when I say ‘all’. If a conversation/meeting/presentation is important enough, you can afford to spend a couple of hours on research, and you can probably make it through dozens if not scores of pages/documents on the topic, which should be enough (assuming you already have a general grounding in the subject), to be able to at least converse intelligently about the specific topic in question.
[5] I use the word ‘hostile’ in the sense of ‘opposed goals’, not necessarily that they would be emotionally hostile. They would just be uninterested in working with you on a solution, hence their use of obstructive or adversarial rhetorical techniques.
tl;dr: Get COVID as few times as you can. Getting COVID the second time is just as likely to kill or disable you as the first time. COVID killed more people in Canada in 2022 than 2020 or 2021, and is disabling many more in an ongoing way. Use masks and better-filtered air to get COVID as few times as you can, and if you do get it, rest up for as long as you can while recovering.
It’s now been more than three years[1] years since COVID-19 entered the world stage, and it’s worth a few minutes to take stock of what we know, where we are, and what we should be doing next.
Acute symptoms vary widely, from respiratory such as cough, fever, shortness of breath, and congestion/sputum, to musculo-skeletal with muscle & joint pain, headache and fatigue, to gastro-intestinal with abdominal pain, vomiting and/or diarrhea. Neurological (separate from nasal congestion) loss of taste and smell is perhaps the most well-known distinctive COVID symptom, made famous by online reviews of scented candles.
These acute symptoms also include death, although the exact number is difficult to measure for a number of reasons[2]. The official ‘Case Fatality Rate‘[3] is generally measured to be around 1%, for example by the John Hopkins dashboard. Taking estimated numbers of non-tested and asymptomatic individuals into account, the actual overall ‘Infection Fatality Rate’ is generally calculated to be between 0.5-1% for ‘wild type’ virus. This rate is modified by age, risk factors, variant of interest (Alpha/Delta/Omicron/XBB1.5/etc), and vaccination status.
2) Protect yourself like a Billionaire; get and use HEPA filters, and use COVID tests if you must gather: At the Davos World Economic Forum this year, there were stringent and multi-layered anti-COVID precautions, including masking, improved ventilation and filtration, and mandatory testing with immediate revocation of access on positive test.
The end to COVID may still not be in sight yet, but we now have a lot more information about how to protect ourselves from it, and maybe, just maybe lighten the load on our overloaded and buckling healthcare system. It is possible to get back to the low case counts of mid-2021, we just need to work together and make sensible decisions. Stay safe out there.
The best current study on the dangers of reinfections: “Long COVID after breakthrough SARS-CoV-2 infection”, Nature Medicine, 25 May 2022
Some quotes from the above two references:
“The organ damage experienced by patients with long COVID appears durable, and long-term effects remain unknown.”
“Cognitive impairments in long COVID are debilitating, at the same magnitude as intoxication at the UK drink driving limit or 10Â years of cognitive ageing73, and may increase over time, with one study finding occurrence in 16% of patients at 2 months after infection and 26% of patients at 12 months after infection74”
“Few people with long COVID demonstrate full recovery, with one study finding that 85% of patients who had symptoms 2 months after the initial infection reported symptoms 1 year after symptom onset143. Future prognosis is uncertain, although diagnoses of ME/CFS and dysautonomia are generally lifelong.”
“The findings highlight the clinical consequences of reinfection and emphasize the importance of preventing reinfection by SARS-CoV-2.”
Other references and links in-line
A final word from r/wallstreetbets and the Bureau of Labor Statistics:
[2] Reasons why the number of deaths from COVID is difficult to measure include undercounting for reasons such as due to delayed or incomplete reporting of deaths due to institutional overload, delayed annotation of cause of death, and the fact that ‘coroners’ are a profession with inconsistent regulations and training requirements. Overcounting can occur when a person would have died anyway, or COVID is counted as one of a group of causes of death for that person. For this reason, ‘excess deaths’ are typically used in case of pandemic or war.
[3] ‘Case Fatality Rate’ is generally measured as (# of deaths confirmed attributed to COVID)/(# of cases of COVID detected). Incorrect attribution of cause of death can move this number in either direction (although measuring ‘excess deaths’ can help), and reducing the level of testing can lead to this number being overstated (you can look at the ‘test positivity rate’ to get a sense of how under-tested the population is (or how bad the outbreak is)). ‘Case Fatality Rate’ is generally assumed to be an overstatement of the fatality rate, if there are a large number of undiagnosed cases in the population, which are taken into account in the probably more accurate ‘Infection Fatality Rate’.