Developer at Microsoft since 1999. I work on HoloLens. I work to get more people, especially women, into computer science. I play ice hockey, and have 3 kids. Check out my #EvilPlanToSaveTheWorld.
I agree about the costs, and I don't think your proposal is too onerous. I'm not sure it would make a real difference, to be honest. Like any test, people would cram, then forget everything after they've passed.
If you ask me, this is one of the greatest arguments for getting as much diversity (of all kinds) into software teams as possible. Overconfidence of one person is usually tamed by others. Overconfidence of a team and a system requires groupthink that happens more easily when there's too little diversity of thought and perspective.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
I agree that my idea probably wouldn't do much. My argument was structured to respond to the claim that any change would stifle innovation.
I don't know how we'll get there but we'll probably end up with some kind of governing and licensing body as software becomes more important, takes on more responsibilities of consequence, and as the profession matures. If you wanted to look into a crystal ball, I'd guess that we'll end up with something similar to what engineers have and it will probably only apply to developers doing higher risk stuff at first.
I had never thought of the diversity argument. Thank-you. I'll have to think about that.
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.
I agree about the costs, and I don't think your proposal is too onerous. I'm not sure it would make a real difference, to be honest. Like any test, people would cram, then forget everything after they've passed.
If you ask me, this is one of the greatest arguments for getting as much diversity (of all kinds) into software teams as possible. Overconfidence of one person is usually tamed by others. Overconfidence of a team and a system requires groupthink that happens more easily when there's too little diversity of thought and perspective.
I agree that my idea probably wouldn't do much. My argument was structured to respond to the claim that any change would stifle innovation.
I don't know how we'll get there but we'll probably end up with some kind of governing and licensing body as software becomes more important, takes on more responsibilities of consequence, and as the profession matures. If you wanted to look into a crystal ball, I'd guess that we'll end up with something similar to what engineers have and it will probably only apply to developers doing higher risk stuff at first.
I had never thought of the diversity argument. Thank-you. I'll have to think about that.