

My dad’s Mercedes indeed beeps incredibly loudly (anyone sleeping immediately wakes up in a panic) if the blind spot sensor goes off… which it does as soon as you put your blinker on.
Guess what that wonderful bit of tech taught my dad to do? That’s right, don’t use the blinker to change lanes if you don’t want your eardrums blown out.
The fundamental problem is that car manufacturers aren’t being held liable for the accidents caused directly or indirectly by these “safety” systems. There is zero oversight and no mandate to investigate false positives of these systems, even when they cause an accident. The end result is that for the manufacturers the point is not to improve safety but to do obnoxious safety theater so regulators look away from rising pedestrian deaths. “Sure our cars are one ton heavier, but they have automatic braking soooo we’re good right?”
Who knows if these gadgets actually do anything or even if they don’t decrease overall safety. The manufacturer gets positive marketing, throws the regulator off their scent, and isn’t held liable for shit when the “safety” system fails or encourages bad habits. Win-win-win. Except the general public loses. But who ever cared about these schmucks?



THANK YOU.
I migrated services from LXC to kubernetes. One of these services has been exhibiting concerning memory footprint issues. Everyone immediately went “REEEEEEEE KUBERNETES BAD EVERYTHING WAS FINE BEFORE WHAT IS ALL THIS ABSTRACTION >:(((((”.
I just spent three months doing optimization work. For memory/resource leaks in that old C codebase. Kubernetes didn’t have fuck-all to do with any of those (which is obvious to literally anyone who has any clue how containerization works under the hood). The codebase just had very old-fashioned manual memory management leaks as well as a weird interaction between jemalloc and RHEL’s default kernel settings.
The only reason I spent all that time optimizing and we aren’t just throwing more RAM at the problem? Due to incredible levels of incompetence business-side I’ll spare you the details of, our 30 day growth predictions have error bars so many orders of magnitude wide that we are stuck in a stupid loop of “won’t order hardware we probably won’t need but if we do get a best-case user influx the lead time on new hardware is too long to get you the RAM we need”. Basically the virtual price of RAM is super high because the suits keep pinky-promising that we’ll get a bunch of users soon but are also constantly wrong about that.