Ironically enough Aurora city water consistently wins awards for it’s quality lol.

I think the legitimate reason is that Aurora is a physically massive city, has lower housing costs than the rest of the metro area, and Denver has a habit of forcing its homeless population out and into Aurora. The police department is also an absolute good ole boys club who are all terrified of city residents to the point where they drive unmarked/undercover vehicles by default (at least it seems that way, I see so few marked police cars but whenever there’s a collection of cop cars with lights going the majority are the undercover)

Sauce: Current Aurora, CO resident. It’s not all bad

If Wells Fargo had amazing management, was a massive and undeniable benefit to humanity, and every one of their employees loved working there, how precisely would that have changed the outcome here?

The only two things that I can think of that would have changed what happened is 1) Security actively monitored every single person’s activity within the building at all times and make notes so one of the security team would notice that she’s been slumped over for a long time, and 2) management insisted that all team members are in office every single day to ensure that they all can see each other. In today’s work culture, I’d argue that doing either of those things is bad management.

You say the point is that it happened at Wells Fargo, but let’s be more clear here: is your goal to find any reason to help justify your distaste of Wells Fargo?

I do believe Wells Fargo has a lot to answer for, but let’s be honest and just in what we go after companies and people for. If we constantly attack entities we don’t like for anything that on first pass sounds bad, eventually we’ll have called wolf too many times and legitimate complaints will get ignored

I really don’t think Wells Fargo has any blame in this, this just as easily could have happened to any company. Perhaps it is a problem with corporate America, but what would you say they’re actually negligent of?

it may sound callous and cold, but logistics does end up asking strange questions like “What is a reasonable amount of time to notice that an employee passed away at their desk in a corporate office?” Or “How do we verify that every employee in the building is still alive?”

It’s unfortunate and sad what happened to this woman, but I don’t see how Wells Fargo played any part in this other than to be a rage-bait headline

God dammit, I lost my ocarina!

Embedded systems run into this a lot, especially on low level communication busses. It’s pretty common to have a comm bus architecture where there is just one device that is supposed to be in control of both the communication happening on the bus and what the other devices are actually doing. SPI and I2C are both examples of this, but both of those busses have architectures where there isn’t one single controller or that the devices have some other way to arbitrate who is talking on the bus. It’s functionally useful to have a term to differentiate between the two.

I’ve seen Master/Servant used before which in my experience just trips people up and doesn’t really address the cultural reason for not using the terms.

Personally I’m a fan of MIL-STD-1553 terminology, Bus Controller and Remote Terminal, but the letters M and S are heavily baked into so much literature and designs at this point (eg MISO and MOSI) that entirely swapping them out will be costly and so few people will do it, so it sticks around