48,108 karma · joined December 14, 2014
And if I were the king of the forest, all medium to large appliances would run a controller board that is pin compatible with either arduino or raspberry pi so that the hobbyist community can refurbish devices that experienced a short. I won’t even make everyone pick a single standard. Two or maybe even three (ESP) are fine as long as we aren’t doing all custom just to count down a timer, run a pump, and sense water levels all at the same time.
Maybe not a space heater but dishwashers for sure. I’m divided stand mixers. Someone more invested could sway me either way.
Same brand as my smoke detectors.
Make sounds that can be detected directionally, assholes.
I’ve lost all respect for people who do shit like this.
When I was just starting out, client-server was still a bit of a specialty, mostly reserved for gaming and large institutions. Most of my education was in single task computing. If the university hadn’t offered a class in distributed computing I wouldn’t have gotten much in that direction except in independent study.
In the time since then, we seem to have focused much less on seconds per task and more on tasks per second, which results in more concern about statistical spreads, and queuing mechanisms to manage the variability between a hit and a miss. It would be better if this sort of computation were more organized into a discipline.
1) the line between toggle and reloadable config is always fuzzy, in part because you don’t know for sure if it’s a toggle until users give their feedback. About half a percent of toggles stick around in perpetuity as either preferences or emergency relief valves for the operations team. That seems small but when you are doing CD aggressively that’s happening to you once a month or every few weeks which makes it a constant companion.
2) you need a system to track and complain about old toggles. If they survive the end of the Epic that birthed them, they become immortal. And you can see variations on Knight Capital play out when they get toggled years after they were supposed to be static.
Part of my last job was winnowing down a convoluted feature toggle system, rebuilding parts of it on top of a FOSS library that did a fraction of the same work. It had become convoluted enough though that it was materially affecting both our deployment time and our cluster density.
To be a little fair to the original author, despite not really respecting him, I had to file a couple serious PRs upstream to simplify the most tortured parts. He worked around a couple of bug/misfeatures but took the scenic route to do it. Guy “never met an abstraction he didn’t like” is not true because his favorite thing was replacing one abstraction with three. And he was one of those guys who learned big words all from books and so he used definitions nobody under 65 has ever used in conversation.
There are bugs. You photographed bugs. Maybe more than you would have without lights at all, maybe about the same.
Also better lights don’t necessarily mean perfect lights. We do lots of things to reduce harm. Unfortunately sometimes we do them too much and conserve a significant fraction of the original harm by increasing demand.
You didn’t tell me to do that, so I am not doing it.
You didn’t tell me not to do this, so it’s done.
I say that as someone who sees Knuth as problematic in other respects starting in the 2010’s. Physics governs so much of computational complexity now that I think the idealized form he presents has transitioned from merely holding us back to being crippling. Only game designers, hyperscalers, and an esoteric few of the rest of us seem to understand the vast gulf between theory and practice that has developed in the five orders of magnitude that compute power has experienced since his first edition.
Many, many things that are considered constant in his world are instead logarithmic to the size of the data being managed, or in the case of very large data sets, order n^1/2 because of speed of light and thermodynamics. That vastly reorders the toolbox, because second shelf algorithms now rival or beat the top shelf ones and some options even farther down now become interesting for novel situations.
Inconclusive tests to increase automation and coverage accomplish less than nothing. The opportunity cost, the loss of trust, the conflation of the manual testing surface area, are all worse than doing nothing.
The point of testing is to establish a level of trust. That level doesn’t need to be 100%. It can’t be 100% regardless. So you do what you can, and you solve the remaining problem a different way. But you need to know it’s there to address it, and the smoke and mirrors fight that.
Is that what you intended to type?
Software is not required to support the requirements of every potential user. Only the ones they mean to support. That’s why Porsche and BMW ignore people complaining about how expensive they are. You aren’t their customer and they don’t want you.
Anyone who has ever wielded a wrench should know that implicitly.
Sometimes you just do things and dare the bosses to say something about it. If they had their way they might have changed it back. But it’s already made and it’s not worth the grief to do anything about it. Too many people like or need George.
I suppose it didn’t work that well because as a rule a car or bike hitting a pedestrian is still almost always at fault.
Guess some schools have wiser faculty than others.
Two of the prominent members of our club were hit by a drunk driver outside a small town. Nobody died but bikes destroyed, nasty bruises, cracked ribs and vertebrae.
The driver shouldn’t have still had his license based on previous offenses. But his dad was a politician. Mayor I believe, and had been bailing that piece of shit out of trouble for who knows how long. I bet daddy would stop protecting him if he was on the hook for a couple million in damages. And/or corruption charges.
One of the victims was in fact a lawyer but I think he was property law not criminal.
The compensation to the shops is in the form of steering business to them from their agents when customers call and say they’ve been in a wreck.
They could do the same with tire centers. We offer a discount if you get tires from here or there. But I think the problem is that what those companies want to do is not change your rates except when you have a life event, get a new car, or have an accident. Tires would have your rates going up and down, unless they made a AAA type of deal with tire centers where you show your insurance and they give you a discount for the tires. Which perhaps could work.
I don’t know if it “certainly” would be cheaper for them to administer a program and maybe that’s why they don’t. It still takes manpower and maintenance teams to keep the program running and maybe that’s not worth enough dollars per year.
Also as we discovered from the Firestone/Ford debacle, a safe tire on one model of vehicle is not safe on another. So you have to do safety research on every vehicle and tire combo.