To be fair to yourself, the fact that C# terminates pending tasks when the main method exits is something most C# devs don’t have to deal with because they’re mostly working in the context of long running servers and apps.
They tend to devolve to the lowest common denominator of what the decision-making chain can understand and resonate with on zero context.
If 1,000 people need to approve the User Journey, you get flights, reminders and docs... because that is what 1,000 big tech employees mutually share as easily understandable common problems within their own corporate zeitgeist.
Disclosure: I work for Meta, and run into this phenomenon daily, but I do not work on Muse.
that seems to be the same problem that most product people in tech have - ie they don't use their own app anywhere close to as much as their average user. all the features they champion happen in walled-garden microcosms loosely backed by heavily p-hacked 'voice of the customer' stats
it's like someone who has a personal chauffeur designing the driving experience of a car - you get educated guesses at best and just total crud at worst. actual epiphanies that happen over repeated use and idle thoughts just don't happen
I find the basic premise for low level code quality to be true, in my experience, but counterintuitively I can now police the overall structure and system architecture MUCH more heavily.
As ever, no one is willing to allocate time for this, but (with unlimited work tokens) I can parallel path massive cleanup refactors all the time now.
