• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • This is actually backwards. Texas Instruments made so many bomb chips that they ended up with a surplus. This allowed them to throw those chips into calculators and edge out any competition with lower prices (because they already made the chips, so they weren’t paying for them.) Then once they had run off all the competition, they jacked their prices up.

    And that, kids, is why the TI-84 costs $100. It’s tech that costs all of $10 to make and program.




  • There is also the hilariously misguided belief that good coders do not produce bugs so there’s no need for debugging.

    Yeah, fuck this specifically. I’d rather have a good troubleshooter. I work in live events; I don’t care if an audio technician can run a concert and have it sounding wonderful under ideal conditions. I care if they can salvage a concert after the entire fucking rig stops working 5 minutes before the show starts. I judge techs almost solely on their ability to troubleshoot.

    Anyone can run a system that is already built, but a truly good technician can identify where a problem is and work to fix it. I’ve seen too many “good” technicians freeze up and panic at the first sign of trouble, which really just tells me they’re not as good as they say. When you have a show starting in 10 minutes and you have no audio, you can’t waste time with panic.




  • I’m a venue manager. If Trump’s team wanted to organize a rally at my venue, (and I was forced to allow it), I would require 100% payment in full before they were allowed in the building.

    In fact, my building collects a refundable cleaning/damage deposit, and I would intentionally over-estimate everything about the event; We estimate the event costs and require clients to pay up front. Then any overages can be claimed from that deposit, or invoiced after the event. Equipment costs, labor needs, room rental times, catering commission, merch commission, etc…

    I would intentionally over-estimate all of that. So when they inevitably have some overages, (like maybe they use more mics than expected, or maybe they show up two hours early), those are already paid for in their initial payment. Then I’d just return any unused overages with the deposit, which is SOP. Because I know that if I had unbudgeted overages and tried to invoice after the fact, I’d never see a single cent.










  • At least on iOS, it takes it a step farther and tells you specifically when an app is accessing your location, microphone, camera, etc… It even delineates when it’s in the foreground or background. For instance, if I check my weather app, I get this symbol in the upper corner:

    The circled arrow means it is actively accessing my location. And if I close the app, it gives me this instead:

    The uncircled arrow means my location was accessed in the foreground recently. And if it happens entirely in the background, (like maybe Google has accessed my location to check travel time for an upcoming calendar event,) then the arrow will be an outline instead of being filled in.

    The same basic rules apply for camera and mic access. If it accesses my mic, I get an orange dot. If it accesses my camera, I get a green dot.