In the workplace we don't write katas, thats all there is to it... We have tools that we are able to offload most of the specificity required for real programmi

In the workplace we don't write katas, thats all there is to it... We have tools that we are able to offload most of the specificity required for real programming => Code examples, Documentation, Stack Overflow, IDEs, etc. ... This is both efficient and lazy. There's also nuance to the "fizzBuzz" thing that people always leave out when they say that developers can't do "a simple fizzBuzz". Things like => It needs to be done on a whiteboard w/o syntax errors, they give FizzBuzz a significant variation, a requirement is slipped in to have fizzBuzz print on the same line when 15s come up, tons of things that make "a simple fizzBuzz" not so simple to pass if people aren't paying attention. Gun to their head, IDE in hand, and stack overflow at their beckon, the vast majority of those programmers wouldn't have a problem stringing together fizzBuzz... but thats not really the question being asked in an interview now is it?