Nah, low center of gravity with nimble handling is better. I'll take an all wheel drive S4, ATS, C class or 3 series over an SUV any snowy day. Sport sedans have swagger too, the only swaggerific SUVs are the Escalade, Cullinan, Urus, Porsche SUVs. But those are out of the price range most of humanity can afford to buy within. I have never had a problem seeing traffic.
> I'll take an all wheel drive S4, ATS, C class or 3 series over an SUV any snowy day
I hope you're putting on the correct type of tires for snowy days. A lot of those models come with summer/performance tires which are incompatible with snow. For my S4, I have a set of Bridgestone Blizzak snow tires that I use during the winter months.
What percentage of ships had fires in their coal holds on the day the titanic launched, by your estimation? I'm struggling to understand how rare a persistent coal fire was during that era. Would they in deed be forced to burn the coal, would this also force a high speed? If I'm to believe what LEO has me, speed is an enormous factor in all accidents, one of the most impactful variables, reduce it to 0 and you get the authors point.
Did the offer any moral or ethics explanation? How did they justify this on a human level? That always interests me about this sort of decision, surely they had many meetings on the topic, what would those minutes look like?
Sure, and man are the easy wins satisfying. Fixing shitty data access methods/patterns is one of the easiest ways to get a "WOW!" out of a client or product owner if you're stuck in the low-visibility silo of backend dev[0]. I've just been repeatedly surprised over the years at how very, very many people are making real money, and consistently finding work, yet don't seem to know which way is up. And I don't mean greenhorns, though often they're given comical levels of responsibility (typically by the cash-strapped or cheapskates) resulting in some real messes, which has a similar effect to when an incompetent "lead architect" or an experienced team nonetheless without a clue between them is set loose, which is just as common.
I harbor no ill will toward these folks. Hell, selfishly, I'm glad there are so many. Having half an idea what you're doing is guilt-inducingly easy, pays amazingly well—especially after the confidence-boost and resulting swagger and negotiating attitude that comes with seeing this kind of thing over, and over, and over, for years on end—and it's disturbingly easy to be a or the "smart one" in the room when you're kind of a dummy, in fact.
[0] Dear backend devs: if you don't simply love backend work and/or if you aren't very well appreciated compensation-wise, and especially if you have long-term career aspirations that involve shifting more toward the biz/architect/management side for the extra social status and higher late-career pay (in most of the industry outside the huge West-coast tech companies, anyway), consider moving to more high-visibility pastures—though ideally not web frontend, as, incredibly, it's still a trash fire and comp is so-so, mostly. Unless you just like trash fires, which some people do.
Mobile, probably a lot of data-analysis jobs provided you get to present results. Desktop work if you can get it. Non-traditional UI like voice. You can spend (what will seem like) a silly amount of time selling what you've done in backend work, even, it's just a harder path.
