Software Gore
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)
- This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
- Please keep all discussions in English. This makes communication and moderation much easier.
- Only post content that's appropriate to this community. Inappropriate posts will be removed.
- NSFW content of any kind is not allowed in this community.
- Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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!
- Tech Support: For all your tech support needs! (partnered)
- Hardware Gore: Same as Software Gore, but for broken hardware.
- DiWHY - Questioning why some things exist...
- Perfect Fit: For things that perfectly and satisfyingly fit into each other!
view the rest of the comments
This, right here, is why "professional" software "engineers" should be licensed.
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.
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.
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
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.
Ok, stated that way it makes more sense, thanks for the explanation
Don't think that kind of thing is going to happen, though
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.
You don't have to have a college degree to become a licensed P.E.; it just takes more years working under the supervision of one. (I think it's something like your options are a bachelor's degree + 4 years P.E. supervised experience or 8 years P.E. supervised experience alone.)
In software "engineering," sure. In e.g. civil engineering, on the other hand, pretty much everybody's either gonna be licensed or on the path to it.
I guess the regulators don't consider software to count as real engineering, LOL!
You conspicuously left out local jurisdictions, and guess what: that's where the requirements kick in (except maybe for trivial stuff, the city or county is going to want plans to have a P.E.'s stamp on them before they'll issue a building permit).
Also, NCEES certification and professional licensure isn't the same thing, so your claim was kind of a red herring in two ways. Licenses are issued by the state.
LOL, you're just quibbling to be argumentative. Are you going to try to make an argument that having 100% of local jurisdictions βοΈ"decide"βοΈ βοΈ"on their own"βοΈ to conform to nationwide standards of practice instead of having a "central system [of] regulation" makes any meaningful, practical difference, or are we done here?
Let me tell you some shocking news: Most of the majors in Computer Science and Engineering (in the university I took it, one of the most prestigious in my country) don't know shit about software engineering. They know only how to burp out the same leetcode style programs they were taught and that's it. I'd trust a guy that managed to learn software engineering on it's own through years of FAFO than (most) university majors.
They don't look like the one who is getting overly-emotional here.
That was supposed to be funny? Are you sure?
One of those was you, so 13 actual opinions that matter.
Compared to the 44 that didn't find it funny at all.
I'm not sure 'people agree with me' and 'they think I'm funny' mean the same thing.
I apologize. Clearly, you are the world's new George Carlin. I'm just unable to understand a wit like yours. But I am glad that you put that you were being sarcastic in all caps. Jokes are always funnier if you explain that they're jokes, so that's probably why those 13 people thought it was so hilarious.
Yes, I know, as I said, I'm really glad you put 'SARCASM' in all caps like that at the end so everyone would know it was a joke because that's what makes jokes funny.
In fact, it would have been even funnier if you had started it with "THIS IS A FUNNY THING I WILL TYPE NEXT:"
You should probably edit your post and add that in for maximum humor. Think how many upvotes you would get to brag about then!
Well that's good, because I certainly haven't said anything funny. I mean, if I did, I would have notified you in all caps.
When you get near a sentence that makes sense, let me know.
Paid*