I think the problem I have with fizzbuzz sorts of code 'challenges' is that it shouldn't be about if you got the right answer but more of how you go about findi

I think the problem I have with fizzbuzz sorts of code 'challenges' is that it shouldn't be about if you got the right answer but more of how you go about finding the right answer; getting requirements, understanding the requirements, and coming up with something close to those requirements even if it's wrong. Instead, I've seen from other people's anecdotes is it's more treated as a standardized test for aptitude and it's just a bad approach to treat them as such. All the binary right/wrong approach proves is that some people aren't quick thinkers or they're bad test takers. In my own brief experience of a few years in programming professionally, the real world is rarely about binary right/wrong and more like iterative less wrong in terms of developing applications. The latter approach requires the ability to self-correct, seek solutions from others when you're lacking knowledge, and knowing when to tell your superiors that something contradicts earlier, mandatory, requirements of an application. So, I don't blame people pushing back against the HR-woo that's creeping into IT. Simply put, if a company thinks programming is like reciting all the capital cities of the United States and Territories then they have no clue what programming is about and maybe they should get out of that business altogether.