• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle
  • 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




  • 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



  • For graphics, the problem to be solved is that the N64 compiled code is expecting that if it puts value X at memory address Y it will draw a particular pixel in a particular way.

    Emulators solve this problem by having a virtual CPU execute the game code (kinda difficult), and then emulator code reads the virtual memory space the game code is interacting with (easy), interprets those values (stupid crazy hard), and replicates the graphical effects using custom code/modern graphics API (kinda difficult).

    This program is decompiling the N64 code (easy), searches for known function calls that interact with the N64 GPU (easy), swaps them with known valid modern graphics API calls (easy), then compiles for local machine (easy). Knowing what function signatures to look for and what to replace them with in the general case is basically downright impossible, but because a lot of N64 games used common code, if you go through the laborious process for one game, you get a bunch extra for free or way less effort.

    As one of my favorite engineering phrases goes: the devil is in the details


  • Having grown up and still have the majority of my family live in rural areas, you’re correct in that there’s a mentality that animals are tools, a means to an end. But I don’t think many with that mentality will be forgiving of her for this.

    With that mentality there is also a general understanding that these are “dumb animals” who can and will fuck up and especially hunting dogs need a lot of training. A dog who fails the training isn’t usually put down, just either given some less strict job, kept as a pet or put up for adoption. Taking her at her word, it sounds like the dog had killed some chickens and had turned towards her and tried biting. But being the dog was only 14 months old, sounds like it had an excited temperament and hadn’t learned just how much bigger than other animals it truly is. Hardly a reason to kill an animal, even if it was just raised as a tool.





  • So many people forget that while they understand how to use a Linux terminal and how Linux on a high level works, not everyone does. Plus, learning all of that takes time, effort, and tenacity, which not everyone is willing to do. Linus’s whole conclusion was that as long as that learning curve exists and as long as it’s that easy to shoot yourself in the foot, Linux desktop just isn’t viable for a lot of people.

    But Linus has done a lot of public fuck ups therefore everything he says must be inherently wrong.