Okay, nice try with the accountant writing Excel macros already being licensed - how about a junior intern writing those Excel macros? ... not licensed in anyway, but he/she does write code.
So my argument remains - how do you define which devs or coders or whatever are required to get that official license, and which don't ... software development is just way too broad an activity and an industry to be regulated centrally, it's going to cause a ridiculous amount of cost, hassle and bureaucracy with hardly any tangible benefits.
The only thing I can imagine is that you could require this for very narrowly defined areas of expertise within the software development industry, for instance SCADA programmers working on mission critical systems, like I said before. In no way is it practically possible to require this across the board, it isn't even possible to clearly define who is a developer or software engineer and who isn't (too many grey areas and edge cases).
"anybody performing development work, including training AI modules, that has a material impact on financial statements or other regulated areas of operations"
So, that does not sound like a blanket across-the-board entry exam or license for every developer (if 'developer' can even be clearly defined) - it sounds like specific requirements or certifications for specific industries or roles, so for situations where it matters.
That's different from what you said before, and now we're getting pretty close to agreeing on this, because under those circumstances I could see the merits of licensing or certifications. But, we're then talking about a much more narrowly defined segment of "hard core devs working on mission critical stuff".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Okay, nice try with the accountant writing Excel macros already being licensed - how about a junior intern writing those Excel macros? ... not licensed in anyway, but he/she does write code.
So my argument remains - how do you define which devs or coders or whatever are required to get that official license, and which don't ... software development is just way too broad an activity and an industry to be regulated centrally, it's going to cause a ridiculous amount of cost, hassle and bureaucracy with hardly any tangible benefits.
The only thing I can imagine is that you could require this for very narrowly defined areas of expertise within the software development industry, for instance SCADA programmers working on mission critical systems, like I said before. In no way is it practically possible to require this across the board, it isn't even possible to clearly define who is a developer or software engineer and who isn't (too many grey areas and edge cases).
Okay, now you're talking:
"anybody performing development work, including training AI modules, that has a material impact on financial statements or other regulated areas of operations"
So, that does not sound like a blanket across-the-board entry exam or license for every developer (if 'developer' can even be clearly defined) - it sounds like specific requirements or certifications for specific industries or roles, so for situations where it matters.
That's different from what you said before, and now we're getting pretty close to agreeing on this, because under those circumstances I could see the merits of licensing or certifications. But, we're then talking about a much more narrowly defined segment of "hard core devs working on mission critical stuff".