Talk Like A Duck comments

"Solving the Final Google Treasure Hunt Problem in Ruby" by Adriano

Wed, 25 Jun 2008 04:45:29 -0400

In Processor#initialize I’d replace

@sums = @counts.inject({}) { |hash, count| hash[count] = []; hash}

@sums = Hash.new {|h,count| h[count] = [] }

for readibility.

"Solving the Final Google Treasure Hunt Problem in Ruby" by Dan Mayer

Tue, 10 Jun 2008 23:32:03 -0400

I need to do more little exercises like this. It keeps your mind sharp and thinking in a different mindset. When you get so deep into a larger Ruby app, you start to see and think about code in a different way. Many times in large apps you are also solving less interesting problems, silly business login. Anyways, thanks for sharing your solution.

"Solving the Final Google Treasure Hunt Problem in Ruby" by ciju

Tue, 10 Jun 2008 10:26:24 -0400

here’s a better way. runs in around 0.2 seconds

http://ciju.wordpress.com/2008/06/03/google-treasure-hunt/

"Solving the Final Google Treasure Hunt Problem in Ruby" by vishal

Tue, 10 Jun 2008 02:35:15 -0400

Did any one use the information that the solution set of primes had to continuous in “any other way” except for a brute force search. I would love to hear that…

"Solving the Final Google Treasure Hunt Problem in Ruby" by Rick DeNatale

Sun, 08 Jun 2008 17:10:28 -0400

@Corey,

Yes it was typo in the problem spec. I’ve fixed it.

"Solving the Final Google Treasure Hunt Problem in Ruby" by Peteris Krumins

Sun, 08 Jun 2008 12:50:15 -0400

Really nice solution in Ruby. Also thanks for linking to my solution! :)

Peter

"Solving the Final Google Treasure Hunt Problem in Ruby" by Corey Martella

Sun, 08 Jun 2008 10:01:12 -0400

Very slick, nice work! Not sure if its a typo in the code or problem spec but the last series length is 1161 vs 1167 in the spec vs code.

"What Would You Miss If You Had To Stop Using Ruby and Go Back to Smalltalk?" by Rick DeNatale

Thu, 22 May 2008 11:42:09 -0400

Randal,

Thanks for the correction and minor refactoring.

"What Would You Miss If You Had To Stop Using Ruby and Go Back to Smalltalk?" by Randal L. Schwartz

Thu, 22 May 2008 10:20:00 -0400

Typo and comment:

Your code:

(x = 0) ifTrue:[a] ifFalse[b]

is missing a colon on the second keyword. And I think I’d also write it as:

^(x = 0) ifTrue:[a] ifFalse: [b]

factoring out the common answer op.

Otherwise, great comparison! I’ll be pointing people at it.

"What Would You Miss If You Had To Stop Using Ruby and Go Back to Smalltalk?" by Russell Christopher

Thu, 22 May 2008 09:51:42 -0400

One thing that wasn’t talked about was REST.

From Wikipedia, “Seaside does not follow REST by default. Instead URLs hold session key information, and meaningful URLs have to be generated explicitly.”

I’m sure there are libraries (plugins?) that make REST easier in Seaside. Makes me wish I would have thought to ask during the meeting but I was too busy trying to assimilate other things.