Why isn't it? Any job where enough information can be known to know that someone should be fired or promoted is a job that can be quantitatively measured to some degree.
The entire point to the site is that programming challenges using STDIN/OUT is not how you write code. So yes, you can cheat - but who cares. At least you get to write real code. Not to mention the number of things that can be tested for since you are able to use real testing frameworks.
STDOUT/IN based challenges cause developers to have to program esoteric challenges that they would never see in real life, and write code that they would never use for anything other than a challenge site.
FYI Codewars has nothing to do with talent scouts. It's purpose is exactly the same as yours, except that it has content ranging from beginner to advanced. Did you build your own testing system for this? It seems to be very similar to Codewars.
I haven't tried React but I felt the complete opposite with Vue. I've never written more beautiful front-end code than what I've done in Vue. Did you use .vue files? Did you use a proper state tree like Vuex?
I'm a co-founder of Codewars. We hired 2 full time employees and a few contractors off of Codewars based off of their profiles. Beyond that, I know of a number of users who leveraged Codewars to obtain internships and jobs, utilizing it to get up to speed on languages they hadn't been very familiar with.
This argument doesn't make sense to me. Regardless of how the design is implemented (JS, HTML) - the designer shouldn't care because they are handing off the design to the developer as a pdf, sketch, etc. file. If he/she is both a designer and a front-end developer than great - he/she knows how to code. What's the problem?
It's the best one for doing challenges that use actual test cases. This challenge could easily be ported to that site (and I think there already are a few elevator ones)
Something that I need to call out here. In talking about how to handle the lack of fixed schemas within Mongo, the OP refers to using if/else blocks to get around field name changes. This shows a severe lack of understanding of how to work with Mongo at such a fundamental level. If using Mongoid (which he is) you simply need to run `Post.all.rename(title: :post_title)` to do the schema change. This may seem like a nitpick to some people, but honestly if that concept was lost on the developer then its clear that there is little to no credibility to be had in the reporting of all the other Mongo issues.
I'm glad that the OP is growing as a developer and starting to understand the merits of SQL and why having defined schemas is important. SQL is awesome and its not going to be replaced by NoSQL (at least not fully). However please make sure that you are building the foundation of your understanding by fully grasping the technologies that you are already using.
"Achieve mastery through challenge" is the tagline. The idea here is to push yourself to solve problems you may have not attempted before, and to learn from others by seeing how they solved theirs. I've have personally learned a lot from seeing how other people solve problems, I even learned a lot from creative uses of solving "Hello World" which was a bit of a surprise.
In short: Codecademy is meant for those who want to learn programming. Codewars is for existing programmers who want to get better at programming.
