4 ms·

Still better than calling yourself code wrangler/ JS ninja. Kidding aside, whats stopping software dev from being regulated and certified in 2017? The previous

Still better than calling yourself code wrangler/ JS ninja. Kidding aside, whats stopping software dev from being regulated and certified in 2017? The previous reason I heard of was that tech changes too rapidly to be standardized.

eru 10y ago
Where's the demand for that? Companies don't even trust university degrees right now. The most a degree gets you is a foot in the door; you'll still have to pass a grilling technical interview process. Making certificates an official requirement just raises artificial barriers to entry, but won't make people actually better. (If you have a good idea for how to certify actual competence, I am all ears. I'd like to upgrade our hiring practices, too. The current prevalent interviewing style puts way too much emphasis on confidence---which works for outgoing people like me, but we are missing out on a lot of good people.)
- vatotemking 10y ago
  I think the presence of this article indicates that there is a demand. > Companies don't even trust university degrees right now. This might be true in the US but may not be in other countries. I just read on a separate comment how the label "engineer" requires a degree in Canada and EU and has legal repercussions if used otherwise. > Making certificates an official requirement just raises artificial barriers to entry, but won't make people actually better. I think it would actually raise the quality of software and bring order/accountability to this otherwise chaotic and "wild west" (ehem JS ecosystem) world of software dev. And the low barrier of entry is a two edged sword. On one side, it does allow more people to code. On the other, more people = more less-talented devs thus more crappy software.
  - eru 10y ago
    I don't know, maybe my perspective is particularly weird: I've been working in Haskell and OCaml most of my career (apart from a stint at Google) which tends to keep out the riff-raff people seem to afraid of, but I don't have a degree.

eru 10y ago

Where's the demand for that? Companies don't even trust university degrees right now. The most a degree gets you is a foot in the door; you'll still have to pass a grilling technical interview process. Making certificates an official requirement just raises artificial barriers to entry, but won't make people actually better. (If you have a good idea for how to certify actual competence, I am all ears. I'd like to upgrade our hiring practices, too. The current prevalent interviewing style puts way too much emphasis on confidence---which works for outgoing people like me, but we are missing out on a lot of good people.)

vatotemking 10y ago
I think the presence of this article indicates that there is a demand. > Companies don't even trust university degrees right now. This might be true in the US but may not be in other countries. I just read on a separate comment how the label "engineer" requires a degree in Canada and EU and has legal repercussions if used otherwise. > Making certificates an official requirement just raises artificial barriers to entry, but won't make people actually better. I think it would actually raise the quality of software and bring order/accountability to this otherwise chaotic and "wild west" (ehem JS ecosystem) world of software dev. And the low barrier of entry is a two edged sword. On one side, it does allow more people to code. On the other, more people = more less-talented devs thus more crappy software.
- eru 10y ago
  I don't know, maybe my perspective is particularly weird: I've been working in Haskell and OCaml most of my career (apart from a stint at Google) which tends to keep out the riff-raff people seem to afraid of, but I don't have a degree.