Comments on: Learning from FizzBuzz: the developer pysche and code reuse http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/ Thu, 18 Mar 2010 02:32:05 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Garry http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137891 Garry Sat, 05 May 2007 17:10:21 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137891 Yup, it's rather hard to find good software developer. But it's possible. Yup, it’s rather hard to find good software developer. But it’s possible.

]]> By: Fizzbuzzing bad for server bandwidth at Lunar Ocean http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137799 Fizzbuzzing bad for server bandwidth at Lunar Ocean Mon, 02 Apr 2007 20:53:30 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137799 [...] Stop losing your time ! Here is what imnsho a good piece of advice. [...] [...] Stop losing your time ! Here is what imnsho a good piece of advice. [...]

]]> By: //engtech http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137716 //engtech Tue, 20 Mar 2007 18:45:24 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137716 <strong>Best of Feeds - 47 links - programming, blogging, career, blog, interview, fizzbuzz...</strong> Tags: Attention, Development, Distribution, Fashion, Photography, Programming, advice, anti-virus, articles, attention, barcamp, blog, blogging, blogs, books, browser, bush, business, canada, career, cartoon, coding, coffee, comic, comics, computerscie... Best of Feeds – 47 links – programming, blogging, career, blog, interview, fizzbuzz…

Tags: Attention, Development, Distribution, Fashion, Photography, Programming, advice, anti-virus, articles, attention, barcamp, blog, blogging, blogs, books, browser, bush, business, canada, career, cartoon, coding, coffee, comic, comics, computerscie…

]]> By: E L Eversman http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137686 E L Eversman Wed, 07 Mar 2007 23:17:50 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137686 Carpundit raised the same question about searching the net for a solution when he pointed out that the Chicago Police Dept. had actually posted a request on its official blog asking if anyone knew why thieves were stealing catalytic converters in Chicago. They figured it might have something to do with the metals used in the parts, hm, like platinum, palladium, and rhodium. Someone posted a couple of explanations from wikipedia enlightening the PD that these are valuable metals for which one can get money in exchange for scrap. I wonder just how much longer Google will be able to hang on to its trademark now that everyone uses the word google as a common verb. Carpundit raised the same question about searching the net for a solution when he pointed out that the Chicago Police Dept. had actually posted a request on its official blog asking if anyone knew why thieves were stealing catalytic converters in Chicago. They figured it might have something to do with the metals used in the parts, hm, like platinum, palladium, and rhodium. Someone posted a couple of explanations from wikipedia enlightening the PD that these are valuable metals for which one can get money in exchange for scrap.

I wonder just how much longer Google will be able to hang on to its trademark now that everyone uses the word google as a common verb.

]]> By: FizzBuzz « danseagrave http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137683 FizzBuzz « danseagrave Wed, 07 Mar 2007 09:41:00 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137683 [...] Just a quick pointer over to more discussion of the FizzBuzz [...] [...] Just a quick pointer over to more discussion of the FizzBuzz [...]

]]> By: raganwald http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137680 raganwald Mon, 05 Mar 2007 20:35:00 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137680 Giles Bowkett has a related viewpoint: http://gilesbowkett.blogspot.com/2007/03/fizzbuzters.html Giles Bowkett has a related viewpoint:

http://gilesbowkett.blogspot.com/2007/03/fizzbuzters.html

]]> By: Joe Harrell http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137674 Joe Harrell Sun, 04 Mar 2007 02:30:46 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137674 I'm forever amazed at how many programmers I know don't seem to be able to effectively use Google to solve problems, or at least point you in the right direction to look. Beats me why one should spend hours playing around with code trying to figure out how to do something when you can do a search on Google or one of the other search engines and come up with something you can work with. Then again, I guess haven't met a lot of people who even know how to effectively use Google to do a search. I’m forever amazed at how many programmers I know don’t seem to be able to effectively use Google to solve problems, or at least point you in the right direction to look.

Beats me why one should spend hours playing around with code trying to figure out how to do something when you can do a search on Google or one of the other search engines and come up with something you can work with. Then again, I guess haven’t met a lot of people who even know how to effectively use Google to do a search.

]]> By: Assaf http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137673 Assaf Sat, 03 Mar 2007 20:37:00 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137673 From one smug asshat to another, here's a secret: if someone did not already give a Ruby solution in one line of code, I would have posted one. From one smug asshat to another, here’s a secret: if someone did not already give a Ruby solution in one line of code, I would have posted one.

]]> By: Peter Cooper http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137672 Peter Cooper Sat, 03 Mar 2007 17:58:42 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137672 Just for kicks I'll tell you why I answered it. I answered it because I saw a) wrong solutions and b) grotesque, overly long solutions.. and I figured I'd be the smug asshat who solves it in a single clean line of Ruby ;-) But, yeah, doing little puzzles is always fun. Just for kicks I’ll tell you why I answered it. I answered it because I saw a) wrong solutions and b) grotesque, overly long solutions.. and I figured I’d be the smug asshat who solves it in a single clean line of Ruby ;-) But, yeah, doing little puzzles is always fun.

]]> By: Lyle Johnson http://labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/comment-page-1/#comment-137667 Lyle Johnson Fri, 02 Mar 2007 17:00:39 +0000 http://blog.labnotes.org/2007/03/02/learning-from-fizzbuzz-the-developer-pysche-and-code-reuse/#comment-137667 A few years ago, I started asking an interview question along the lines of what you're suggesting. I would pick some cryptic error message that I'd run across that morning, or the day before, and ask the interviewee how he or she would go about finding out what the error message meant (and, more importantly, how to fix the problem). I know that, in my experience, the quickest solution isn't tracking down the documentation (if it exists), or going to the source code (if I have it) -- it's almost always just Googling for the error message text and seeing what pops up. If I'm running into this problem, there's an almost 100 percent certainty that someone else has run into the same problem before me. And of course, it doesn't have to be an error message -- it can be any little bit of trivia, or (as in your suggestion) a bit of code, or an algorithm -- whatever. The answers I get to this question tell me a lot about how much hand-holding this person's going to need when they run up against the obscure kinds of problems we all run into when we're coding. A few years ago, I started asking an interview question along the lines of what you’re suggesting. I would pick some cryptic error message that I’d run across that morning, or the day before, and ask the interviewee how he or she would go about finding out what the error message meant (and, more importantly, how to fix the problem). I know that, in my experience, the quickest solution isn’t tracking down the documentation (if it exists), or going to the source code (if I have it) — it’s almost always just Googling for the error message text and seeing what pops up. If I’m running into this problem, there’s an almost 100 percent certainty that someone else has run into the same problem before me. And of course, it doesn’t have to be an error message — it can be any little bit of trivia, or (as in your suggestion) a bit of code, or an algorithm — whatever.

The answers I get to this question tell me a lot about how much hand-holding this person’s going to need when they run up against the obscure kinds of problems we all run into when we’re coding.

]]>