• 0 Posts
  • 611 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle



  • I’ve read a bit about Teflon. My understanding is that the big health hazard is during the application process, primarily for the factory workers - you really don’t want to breath aerosolized uncured Teflon, or get it in your eyes. It’s not the most hazardous industrial chemical out there, I don’t think there’s any particular ethical issue with manufacturing products with Teflon as long as workers are provided PPE. If it’s a sweatshop product well then there are obviously a lot of ethical issues.

    Once it’s cured it’s chemically inert (which is kind of the whole point) - I’m not aware of any research showing that the human body can absorb any harmful chemicals from cured Teflon - basically your stomach acid and digestive tract bacteria can’t do anything to it. You shouldn’t worry overmuch about being harmed by cooking in a Teflon-coated pan, it’s not a heavy metal or anything like that.

    That said, a deteriorating Teflon coating can be a hazard. The material is fairly stiff and again, your digestive system can’t break it down. Any small particles should (hopefully) pass through, but larger flakes could get stuck somewhere and then… well your body can’t break it down. It’s going to be there causing a blockage until something dislodges it, it’s not going to bend very much, and it might have sharp enough edges to irritate or damage the surrounding tissue.

    And yeah, nothing breaks it down naturally, so it is just going to be in the world forever, gradually eroding into smaller and smaller particles along with all of the other plastic pollution, so yay.

    I can’t point to any specific sources on this, it’s from reading various articles over two decades, I’m definitely not an authority.



  • DuPont. Here’s just a little tidbit:

    Between 2007 and 2014 there were 34 accidents resulting in toxic releases at DuPont plants across the U.S., with a total of eight fatalities.[93] Four employees died of suffocation in a Houston, Texas, accident involving leakage of nearly 24,000 pounds (11,000 kg) of methyl mercaptan.[94] As a result, the company became the largest of the 450 businesses placed into the Occupational Safety and Health Administration’s “severe violator program” in July 2015.

    Monsanto:

    In Anniston, Alabama, plaintiffs in a 2002 lawsuit provided documentation showing that the local Monsanto factory knowingly discharged both mercury and PCB-laden waste into local creeks for over 40 years.[220] In 1969 Monsanto dumped 45 tons of PCBs into Snow Creek, a feeder for Choccolocco Creek, which supplies much of the area’s drinking water, and buried millions of pounds of PCB in open-pit landfills located on hillsides above the plant and surrounding neighborhoods.

    These are the kind of companies that inspired the cartoon villains of the 1980s that just dump pollution because.


  • Beyond your eventual technical solution, keep this in mind: untested backups don’t exist.

    I recommend reading some documentation about industry-leading solutions like Veeam… you won’t be able to reproduce all of the enterprise-level functionality, at least not without spending a lot of money, but you can try to reproduce the basic practices of good backup systems.

    Whatever system you implement, draft a testing plan. A simpler backup solution that you can test and validate will be worth more than something complex and highly detailed.


  • and you have to choose to boot into desktop mode to even mess with anything.

    You say that like it’s a bad thing, but I think having the two separate modes is a fantastic setup. You get basically a console experience, smooth and straightforward and easy to use for just playing games, and you still have access to the underlying system anytime you want.





  • ever since libraries have been a thing, the majority of developers have just used the libraries without really understanding what goes on inside them. And that’s not necessarily a bad thing — the entire point of abstraction is so that developers can focus on the stuff they need to get done while ignoring the already solved problems.

    Nobody but nobody has time to know what’s in every library they might need to use. Who among us truly understands their network stack, all 8 layers?

    senior devs have to spend all their time doing code reviews and editing and refactoring codebases that nobody else understands.

    That’s OK we will just train AI to review and refactor for us! I’m sure everything will be fine.

    Vulnerable code will be with us forever. The system will always be Swiss cheese. If you think you understand common mistakes, enough that you can review other peoples’ code for them, there’s work for you in infosec for sure.