| ▲ | sigseg1v 7 hours ago | |||||||
We require someone with a professional engineering designation from an accredited engineering body to sign off and approve before a building can be built. If it is found to have structural issues later, that person can be directly liable and can lose their license to operate. Why this is not the case with health software I cannot explain. Every time I propose this the only argument I recieve against it is people who are mad that their field might dare to apply the same regulation every other field has. | ||||||||
| ▲ | consumer451 7 hours ago | parent | next [-] | |||||||
Oh man, I have gone off on rants about software "engineering" here in the past. My first office job was as an AutoCAD/network admin at a large Civil and Structural engineering firm. I saw how seriously real engineering is taken. When I brought up your argument to my FAANG employed sibling, he said "well, what would it take to be a real software engineer in your mind!??" My response was, and always will be: "When there is a path to a software Professional Engineer stamp, with the engineer's name on it, which carries legal liability for gross negligence, then I will call them Software Engineers." | ||||||||
| ||||||||
| ▲ | EdNutting 7 hours ago | parent | prev | next [-] | |||||||
Totally agree - not just medical software either. See replies to my other comment threads. Software engineers really don’t like the idea that they might have to show they can perform at a certain standard to be able to work as a software engineer. Typically arguments come up: “that’s gatekeeping” - yes, for good reason! “Laws already exist” - yeah, and that’s not the same as professional accreditation, standards and codes of practice! Different thing, different purpose. Also the laws are a mishmash and not fit for purpose in most sectors. | ||||||||
| ▲ | 7 hours ago | parent | prev [-] | |||||||
| [deleted] | ||||||||