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

help-circle

  • We have forced it, quite hamfistedly, to do anything. The organic hell-evolution of web browsers turned them into do-anything sandboxed mini-OS. It meant whatever hellish code you used to write your corporate mandated web app could now become a perfectly bloated standalone application. And the demonic language that would enable it was called Javascript. It does the backend and it does the frontend. You could consider those advantages over other devices, like toasters and those handheld electronic games from the 80s.


  • It kinda comes out of the experience. There’s an outstanding Github issue that notes that a specific version of YT Music is broken past a certain version. Most of the patches fail to apply and you just get the minor ones. You can use the version just before with no issues. How can you litigate against lines of code that don’t even work? This is similar to the vulnerability that Yuzu gave up since they offered Patreon-exclusive updates to support a leaked BOTW:TOTK .iso. Easy to prove your intent there.




  • sincle354@kbin.socialtoLinux@lemmy.mlXZ backdoor in a nutshell
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    7 months ago

    So it’s not that the Volkswagen cheated on the emissions test. It’s that running the emissions test (as part of the building process) MODIFIED the car ITSELF to guzzle gas after the fact. We’re talking Transformers level of self modification. Manchurian Candidate sleeper agent levels of subterfuge.



  • From a software engineering view: Lots of rebuilding the wheel, now with Internet Explorer dependencies. Large tech firms are more and more bureaucratic rather than innovative. Startups slurp up VC funding for the next 200 or so unicorn investments. NVIDIA is THE ENTIRE S&P 500 at this rate with SERIOUS “Peak of Inflated Expectations” valuation. Elon Musk.

    All the while the majority of the job is fixing the mistakes of the past, of yourself and of some code monkey in 2003. There’s this theory that code replicates the structure of the design team. When that team spans an entire corporate hierarchy with SCRUM standups every 2.5 milliseconds, you wonder if you could do the equivalent of the ending of Office Space to the codebase.

    I’m sorry, I’m just… anyway, a sage piece of advice. For the love of all that is holy, write requirements BEFORE doing validation for Aerospace applications, and DO NOT OUTSOURCE THE REQUIREMENTS WRITING. That is all.






  • Always glad to brush up on my acts of mass terrorism/righteous defenses of sovereignty*.

    *Note: This is barely a funny, I legitimately have nowhere near enough knowledge on the topic, not even superficially. 14,000 words of Wikipedia article spanning 4 centuries? Just the Wikipedia article? Damn…


  • I’ve got a Linux work server because VHDL simulations are hella expensive. I have to say that if your team isn’t willing to RTF-Man pages, you end up with a lot of cargo cult CLI processes. No crystalized knowledge or training, it’s hard to start up in it. It’s enough that requiring explicit Linux experience for new hires is preferable. Windows sadly has the familiarity benefit. And don’t get me started on the wacky custom solutions the IT set up circa 2002…