This viewpoint seems short-sighted. In the 1940s and 1950s, if somebody were skeptic of lead, you could've replied "Do you paint your home? Get your water from pipes in your house? What about having gas in your car?"
One wears a lead vest when getting x-rays at the hospital or as protective equipment when operating on nuclear reactors.
Moving beyond eating lead doesn't mean not using it intelligently when the risk profile is low. Also, lead-based glass is also an important component of the world's high-efficiency perovskite solar cells.
Many of the industrial products materials we wouldn't want to eat, this just means we have to be better about recycling.
Not sure why x-rays are still being used when there appears to be better and safer alternatives... Specially at the dentist where an inexperienced person shoots them at your head... Thank God they cover your chest with lead though....
> Not sure why x-rays are still being used when there appears to be better and safer alternatives
It all has to do with how medical billing is structured. Xrays were already cheap before the current model was put in place so they are the go to method for diagnostic. Even though there are better ubiquitous options available, price fixing keeps those out of reach for triage and simple diagnostics.
>The developers MUST care for the quality, not outsource it to some external team. The desire of large corps to spend huge amount of $$$ to create artificial roles to water down ownership can never cease to astonish me.
As a former quality-focused dev, I can tell you that the industry beats it out of you with a club. There is always somebody above you who cares only about their own career ambitions and has more leverage than you do. This leads to a horde of devs who just do what they're told and not much else.
Businesses are all about risk management. The safest way to de-risk a business is to water down ownership, at the cost of injuring quality-focused devs. You're only a cog. You need to only be a cog to them. They must to be able to replace you with another cog when you leave for greener pastures.
> I can tell you that the industry beats it out of you with a club.
yep, i can say i've seen this over and over; more than anything incentives are for the next okr or whatever to be completed so they can move on to the next one asap.
i've seen pr's sent out for review that literally didn't work or crashed immediately on use... as if the expectation is qa will report whatever needs fixing but thats fine cause its "in qa now" so development is "done".
