3 ms·
There's been talk in the past of having some levels of certification required to be called a software developer/engineer. I'm not convinced this is a bad thing
by blunte 6y ago
There's been talk in the past of having some levels of certification required to be called a software developer/engineer. I'm not convinced this is a bad thing.
To be a pilot, you have to at least jump through a lot of hurdles and formalities, and some of those will make you better. I think the world of corporate software development could use a few fundamental hurdles.
- InitialLastName 6y agoThe actual engineering professions have professional certifications that you have to attain to be allowed to do much of the (especially safety-critical) work of the profession [0] without supervision. [0] https://www.nspe.org/resources/licensure/what-pe https://www.nspe.org/resources/licensure/what-pe
- Guthur 6y agoThe problem I feels is that we have no decent foundational standards and methodologies to build the software upon like we would a building or bridge. Civil and structural engineering have a lot of the basics abstracted away in to easily reusable knowledge that can be applied from one project to the next. Software engineering sometimes feels like we never managed to pull ourselves much further beyond a Leonardo Da Vinci drawing.
- Guthur 6y agoAlso, we are again defaulting to assume that Pat is the problem here. He's likely an average software engineer, and if not then we've done a terrible job at education, hiring, or promotion, which again is not necessarily his fault. The problem is the system, and certification would potentially resolve some aspects, but he still could be ranking himself incorrectly against other engineers and therefore we might be right back to square one.