kdjkdjk

They do so successfully, but wane quite quickly. Few people are taking booster shots so their protection diminishes over time.

and well, COVID being fundamentally a cardiovascular disease might be an actual alternative explanation :)

Yes and no. More people are also having more health issues because of a weakened immunse system (due to prior COVID infections). The "direct" link might not necessarily be made, but there's definite increased mortality as a consequence of COVID policies.

One day the world will wrap its head around the fact that having COVID affects your immune system long-term and as such is bad for future health outcomes.

Welcome to my TED talk. Wear a mask.

nah, automotive hackers hang around here too ;)

I'm old. I've seen this more times than I can count. There's always a whole lot of assumptions that just never quite pan out as expected, do they ?

Rewrites always end up taking way more time and resources than anticipated, and you'll ultimately end up with something that has fewer features and not necessarily considered "better" by your users. Refactors on the other hand can get you some wins faster, but will probably be abandoned half-way through and as such contribute to the increasing unstability of the code base.

But hey, you're a good cookie, at least you're thinking and asking the questions. I'm sure you can rewrite the codebase cleaner, technically, but can you also pull it off organisationally (long term mgmt committment, sufficient budget, resources, time and priority ?). If you say there are hotfixes by inexperienced programmers, obsolete business requirements, skipped testing etc., you need to ask yourself why that is and how it came to be, and whether you can really pull off a rewrite under the conditions that led to the current situation ?

So yeah, I tend to favor refactoring, at least you'll end up with something.

Also, applicable xkcd: https://xkcd.com/927/

obligatory link: https://news.ycombinator.com/item?id=17164707