Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by meric on Thursday April 09, 2015 @06:51PM
(#9351565)
Either ways the sad reality of where the IT industry stands today is that you don't even need Fizz Buzz to differentiate a bad non-programmer from a good one - Just asking them to print 100 to 1 is usually good enough.
The point of FizzBuzz is to differentiate whether a person is a non-programmer, or a programmer. It is necessary but not sufficient to determine whether a programmer is good. It's important to note non-programmers are not necessarily bad persons, they just aren't programmers.
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by colanderman on Friday April 10, 2015 @12:29AM
(#9352590)
Suggest graphing whining on one axis and coding on the other. Graphing them both on the same axis vs. candidate # is unhelpful. (And you should never connect data points which have no meaningful interpolation with lines. It's misleading.)
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by geebee on Thursday April 09, 2015 @05:32PM
(#9351185)
Couple things.
First, yeah, this should be easy.
Second, yeah, you should do almost anything other than whine. That certainly includes improving your skills.
Third, there's plenty to object to in the hiring process and work environment for many software developers, and I certainly don't think all of it should be dismissed as "whining".
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by wcdolphin on Thursday April 09, 2015 @10:42PM
(#9352316)
Is there something wrong with the following? I feel like I am somehow missing the complexity of the problem. Framing it as "Count down from 100 to 1" makes the implementation read like the problem.
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by TheLoneWolfling on Friday April 10, 2015 @12:25AM
(#9352580)
There isn't any complexity.
It's "just" that there are many people who don't exactly problem-solve well.
I've noticed this before. I've taken classes where people produce decent, although not great, assignments, and then turn around and get <20% on a test.
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by jbergens on Friday April 10, 2015 @06:40AM
(#9353476)
I still view this as a way to separate those who can hardly program at all from those who can. It is probably not a good way to measure if anyone is a great developer. The first part should probably be possible to answer by just talking to the person and to a few people he has worked with.
Besides my main arguments agains this there is another problem with this kind of questions: when the questions become known and people start writing answers all over the net (just look at a lot of comments on this page) someone could learn the answer without being or getting good at programming.
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by nallerooth on Friday April 10, 2015 @02:25AM
(#9352815)
I understand that even simple problems may seem difficult when you're under stress (being interviewed). I know that I perform a lot worse under those conditions than under "normal stress", as I have to prove myself to someone else and not just to myself. But with that said, this shouldn't be a problem for anyone who have been programming for a year or more.
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by Jemaclus on Thursday April 09, 2015 @05:04PM
(#9351013)
Hmm. This post seems to imply that whining correlates with poor coding abilities. I'm not sure I buy that. And as a tongue-in-cheek observation, what does taking the time to write about whining about people not being able to code mean for this guy's coding abilities? :)
Re:Easier Than Fizz Buzz – Why Can't Programmers Print 100 t...
by robkix on Friday April 10, 2015 @09:54AM
(#9354251)
Why reversed range? Range is fully capable of descending [1]
You also missed the point of the exercise: start at 0 in your index, but count backward from 100 in output. So the map is 0->100, 1 -> 99, ..., 99 -> 1, 100 -> 0
The point of FizzBuzz is to differentiate whether a person is a non-programmer, or a programmer. It is necessary but not sufficient to determine whether a programmer is good. It's important to note non-programmers are not necessarily bad persons, they just aren't programmers.
Am I coldhearted for thinkng this is were you end the interview and go back to your desk to get some work done?
They might be very nervous, having a bad day, etc.
for ( int i = 0144;
or
for ( int i = 0x64;
Unfortunately, the constraint was "for ( int i = 0;". :-/
#include<stdio.h>
int main(){
First, yeah, this should be easy.
Second, yeah, you should do almost anything other than whine. That certainly includes improving your skills.
Third, there's plenty to object to in the hiring process and work environment for many software developers, and I certainly don't think all of it should be dismissed as "whining".
for(int i=0; i< 100; i++){ System.out.println(100-i); }
It's "just" that there are many people who don't exactly problem-solve well.
I've noticed this before. I've taken classes where people produce decent, although not great, assignments, and then turn around and get <20% on a test.
Besides my main arguments agains this there is another problem with this kind of questions: when the questions become known and people start writing answers all over the net (just look at a lot of comments on this page) someone could learn the answer without being or getting good at programming.
However I whine a lot ... but it could be that the situation is really bad at my job.
Am I hired ? :-)
You also missed the point of the exercise: start at 0 in your index, but count backward from 100 in output. So the map is 0->100, 1 -> 99, ..., 99 -> 1, 100 -> 0
[1] https://docs.python.org/2/library/functions.html#range
for($i=0;$i<100;$i++) echo 100-$i."\n";
for($i=0;;) echo 100-$i>0?100-$i++."\n":exit;
for(int i = 0, t = 100; i < 100; i++) { Console.WriteLine(t--); }
Hint: You don't need "t".