Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
Wow you are exactly what he is complaining about. It's not like the guy is coding live and each keystroke goes directly to the machine. What risk is it to people if a couple years ago one of the guys typing keys that would later get tested like crazy was high?
I mean, there are applications where that could be the case. I program PLC’s for a living. Sometimes on live machines running in a plant.
I don’t agree with his overall viewpoint, but he does have a point in this case.
If you're committing on live then I have some choice words for the company you work for and the practices you've been taught
Bro I knew what safe practices are. But the point being that it is entirely possible.
Cheese theory. You want as many layers of protection between creation and execution. Bugs will inevitably slip through tests, and reducing the number that are created before testing will inherently reduce the number that slip through. In some fields preventing just one bug might save many lives.
I would not limit it to coders however - a lawyer screwing up their defense, a coked up billion dollar CEO disregarding the wider effects of a major decision, an insurance agent making a wrong decision etc. etc.
The irony is that people higher up in the chain of command, whose decisions affect far more people, often slip by without being tested whilst the bottom-feeder who gets fired after a fuckup that affects a single person is hounded to the ends of the earth.