this post was submitted on 04 Dec 2023
822 points (98.1% liked)

Software Gore

5321 readers
76 users here now

Welcome to /c/SoftwareGore!


This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!

Remember to read the rules before you make a post or comment!


Community Rules - Click to expand


These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)


  1. This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
  2. Please keep all discussions in English. This makes communication and moderation much easier.
  3. Only post content that's appropriate to this community. Inappropriate posts will be removed.
  4. NSFW content of any kind is not allowed in this community.
  5. Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
  6. Do not repost media that has already been posted in the last 30 days. Such reposts will be deleted. Non-original content and reposts from external websites are allowed.
  7. Absolutely no discussion regarding politics are allowed. There are plenty of other places to voice your opinions, but fights regarding your political opinion is the last thing needed in this community.
  8. Keep all discussions civil and lighthearted.
    • Do not promote harmful activities.
    • Don't be a bigot.
    • Hate speech, harassment or discrimination based on one's race, ethnicity, gender, sexuality, religion, beliefs or any other identity is strictly disallowed. Everyone is welcome and encouraged to discuss in this community.
  9. The moderators retain the right to remove any post or comment and ban users/bots that do not necessarily violate these rules if deemed necessary.
  10. At last, use common sense. If you think you shouldn't say something to a person in real life, then don't say it here.
  11. Community specific rules:
    • Posts that contain any AI-related content as the main focus (for example: AI β€œhallucinations”, repeated words or phrases, different than expected responses, etc.) will be removed. (polled)


You should also check out these awesome communities!


founded 1 year ago
MODERATORS
 

Reminds me of the Therac-25 incident..

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 61 points 11 months ago* (last edited 11 months ago) (3 children)

This, right here, is why "professional" software "engineers" should be licensed.

[–] [email protected] 20 points 11 months ago (1 children)

Former healthcare to software engineer working on a master's here. My colleagues who were licensed back in healthcare weren't all of the same quality. They all made mistakes at one point or another, some pretty bad some minor. There's no difference though, minor could just as well become major.

The way they get around it in healthcare is by throwing more people at the problem. You have a physician who is good at pointing in the general direction of the problem and a solution, then you have all the auxiliary staff who will narrow down on the solution based on their field. But at any single point all of them could fuck up, or one of them could.

Now that I'm a software engineer and I've written enough code to do stuff. I can confidently say that licensing will not solve this problem. Especially if there aren't enough people involved. Which is probably what was missed in the beginning.

Anyway long rant over.

[–] [email protected] 10 points 11 months ago (1 children)

Licensing isn't about magically ensuring that the practitioner won't make mistakes; it's about holding the practitioner accountable for his mistakes, which in theory gives him more incentive to be more careful -- or to change his practice's workflows and systems so as to be better able to detect and correct mistakes.

In fact, I would argue that the "throwing more people at the problem" phenomenon in healthcare is an example of that very thing. Do you think they'd keep staffing levels equally high without licensing? 'Cause I sure don't.

[–] [email protected] 0 points 11 months ago (1 children)

So, what you say is let's hold the lowest level accountable, the person who may don't have any power over the fcked up decisions about the amount of developers, presence of QA, and timeline.

No, licensing will not make "accountable" people magically incentivised enough to make no mistakes

[–] [email protected] 5 points 11 months ago (1 children)

A licensed Professional Engineer is exactly the opposite of the lowest level person. In fact, that's part of the point: giving the experts the power to say "no" to unsafe/unethical management.

[–] [email protected] 1 points 11 months ago

Ok, stated that way it makes more sense, thanks for the explanation

Don't think that kind of thing is going to happen, though

[–] [email protected] 17 points 11 months ago

Never gonna happen as long as the demand is so much higher than the supply.

Perhaps it should be a requirement for certain things though, like the medical area.