[sigsergv]

Software engineers make product, not code. I'd prefer talented developer with good practical experience in “releasing products” rather than an algo-geek who can only solve stupid hiring quizes.

Slow buggy ugly WORKING RELEASED product is a much-much better than ideal clean and effective thing not yet ready for release for a few years in row.

[hackinsack]

Not saying I disagree with that, except for releasing slow buggy code. Why not accept either of those people? There are efficient ways, as described in the article, to interview for people that are great at releasing quality code in a productive time frame. I was simply pointing out that releasing code daily doesn't mean you know what you're doing. If you can't answer at least some of the questions that were in this article, I'd question your ability to write productive code. That's not to say that only questions like that should be a determining factor for ones ability to produce.

[nhangen]

You're right that shipping !== good code, but I wouldn't be able to keep shipping the same product if it weren't somewhat valuable to my customers.

The point isn't that I'm a unicorn, but that good developers can exist outside of code challenges.

People like me, that are self-taught and work super hard in order to improve our craft...we're not appreciated enough.

Everyone wants a rockstar, forgetting that drummers and bass players add a lot of value.