Skip to main content

How are you doing TODAY?

How one extra word can make a big difference…

A question people probably ask you a lot is

How are you doing?

Most of the time, this question is used as a polite way to say hello, and the question asker doesn’t really expect you to say anything about how you are really feeling.  The expected answer is

Great, thank you.

And we follow up by asking the same polite question

How are you doing?


What if...

But what if you add one simple word and change the question to this:

How are you doing TODAY?

Now this question becomes really specific and it creates an opening to let the polite answer pass and give a real answer on how you are feeling in this moment. Although only one word was added I noticed that it was a lot harder for people to just answer with a “Great, how are you?”. At least I noticed a small hesitation before people answered the question reflecting on their answer, at best they opened and really shared what was on their mind.

So my suggestion to you before you start your weekend, give it a try yourself and see how adding one word makes a difference…


Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more