6 ms·

"FizzBuzz is famously hard" Are we talking about the thing of writing "fizz" for multiples of 3 and "buzz" for multiples of 5 and "fizzbuzz" for both, for the

by ktizo 14y ago

"FizzBuzz is famously hard" Are we talking about the thing of writing "fizz" for multiples of 3 and "buzz" for multiples of 5 and "fizzbuzz" for both, for the numbers 1 - 100? If that is famously hard, then the definition of hard must have changed massively while I wasn't looking.

Alex3917 14y ago
If the vast majority of people applying for programming jobs can't solve it, then it qualifies as hard by definition.
- ktizo 14y ago
  It is hard, only in the sense that programming anything is hard, if you don't know how to program. If you can program at all, you can solve it. It definitely wouldn't qualify as 'famously hard'. Things that achieve fame for being hard are usually very very difficult indeed. If anything, in the narrow circles in which it has any fame at all, it is famously easy.
- sopooneo 14y ago
  I agree with your analysis. However I've only ever sat in on a few programmer interviews, and was lucky enough to get only the few that had already made it through several screens and were quite sharp. However, if so many people can't do FizzBuzz, that's baffling. If they can't do that, what can they do? I mean that literally. Do they just have knowledge of certain specific frameworks or something? Can anyone shed light on this? I know this may be derailing the conversation, and it bothers people, I'll not mind deleting this post.
  - snogglethorpe 14y ago
    One issue I've had is that if a question is too easy, I start out thinking "this must be a trick question..." and then tie myself up in knots trying to find the (non-existant) catch... Of course in an interview, one should presumably just say "hey this seems too easy, is this a trick question?" but ...
    - ktizo 14y ago
      That reminds me of when I was first learning to program. I wondered for an embarrasingly long time what the hell 'foo' meant. I knew it must be something really important as it was absolutely everywhere.
Lazare 14y ago
"famously hard" was an example of sarcasm. A lot of people applying for programming jobs can't solve it. Any programmer, pretty much by definition, can. The lesson is that a lot of people who apply for programming jobs can't program. :)

by ktizo 14y ago

Alex3917 14y ago

If the vast majority of people applying for programming jobs can't solve it, then it qualifies as hard by definition.

ktizo 14y ago
It is hard, only in the sense that programming anything is hard, if you don't know how to program. If you can program at all, you can solve it. It definitely wouldn't qualify as 'famously hard'. Things that achieve fame for being hard are usually very very difficult indeed. If anything, in the narrow circles in which it has any fame at all, it is famously easy.
sopooneo 14y ago
I agree with your analysis. However I've only ever sat in on a few programmer interviews, and was lucky enough to get only the few that had already made it through several screens and were quite sharp. However, if so many people can't do FizzBuzz, that's baffling. If they can't do that, what can they do? I mean that literally. Do they just have knowledge of certain specific frameworks or something? Can anyone shed light on this? I know this may be derailing the conversation, and it bothers people, I'll not mind deleting this post.
- snogglethorpe 14y ago
  One issue I've had is that if a question is too easy, I start out thinking "this must be a trick question..." and then tie myself up in knots trying to find the (non-existant) catch... Of course in an interview, one should presumably just say "hey this seems too easy, is this a trick question?" but ...
  - ktizo 14y ago
    That reminds me of when I was first learning to program. I wondered for an embarrasingly long time what the hell 'foo' meant. I knew it must be something really important as it was absolutely everywhere.

Lazare 14y ago

"famously hard" was an example of sarcasm. A lot of people applying for programming jobs can't solve it. Any programmer, pretty much by definition, can. The lesson is that a lot of people who apply for programming jobs can't program. :)