Comments on: Rock Paper Scissors

By: rock smashes scissors « Two Guys Arguing

rock smashes scissors « Two Guys Arguing — Mon, 08 Nov 2010 01:27:09 +0000

[...] almost two months ago I issued a challenge to Ben to implement a silly spec of a problem I had recently been playing around with. The response [...]

By: Challenge – QuickPiet Interpreter « Two Guys Arguing

Challenge – QuickPiet Interpreter « Two Guys Arguing — Sun, 14 Mar 2010 17:10:01 +0000

[...] pair off of Nate’s Rock Paper Scissors challenge, here is one I am offering up to him: create an interpreter which will execute QuickPiet [...]

By: The revenge of the 5 questions « Two Guys Arguing

The revenge of the 5 questions « Two Guys Arguing — Fri, 05 Feb 2010 02:32:04 +0000

[...] TDD. Nate’s recent TDD Rock Paper Scissors challenge and very interesting talks with the guys at CodeMash left me questioning why I work the way I do, [...]

By: benjaminplee

benjaminplee — Tue, 19 Jan 2010 17:37:16 +0000

FYI Mr. Border’s version http://github.com/hborders/RockPaperScissors

By: benjaminplee

benjaminplee — Tue, 19 Jan 2010 17:33:52 +0000

One major thing I got hung up on (and often do especially when writing code test first by myself) is getting hung up on exactly how a test should look, how to best implement something, etc. If you are working with a good pair and not hogging the keyboard this poor discipline will often work itself out and become apparent. But, when working by myself I still find this hard. Instead I should focus on writing small tests that teach me something about the behavior of the system and if I find myself getting stuck in a large refactoring or debating the merit of a test I should refocus on what am trying to do right now, not down the road.

Having a setup that bugs me when the code has been in a failing state for more than a minute or two would be a nice check for this.

By: benjaminplee

benjaminplee — Tue, 19 Jan 2010 17:29:20 +0000

I followed your same basic flow of thinking although I got hung up on how to represent the actual RPS game logic of who wins when playing who and how to implement. This is where a pair complaining that I was doing things too fancy for a first cut would have helped.

One issue I still have on many projects is how to manage large refactorings and managing tests, test contexts, and not losing some test intentions when moving code around.

By: benjaminplee

benjaminplee — Tue, 19 Jan 2010 17:25:13 +0000

Last week I finally finished a first cut at your challenge; sorry for the delay. You can find my codes at http://github.com/benjaminplee/RockPaperScissors/tree/benjaminplee

Currently the base logic is all there and one form of multi-game play (First to X). I am still working on the other 2 multi-game forms when I have spare time.

By: Kevin Berridge

Kevin Berridge — Fri, 11 Dec 2009 02:33:21 +0000

Let me know if this is the kind of insight you’re interested in:
http://bitbucket.org/kberridge/rockpaperscissors/src/tip/RockPaperScissors.Specs/Readme.txt

By: youngnh

youngnh — Thu, 10 Dec 2009 21:08:29 +0000

hey, speed of delivery is a feature. If I was a customer I’d pay extra for that alone.

any insights into how you took a crack at this?

By: benjaminplee

benjaminplee — Thu, 10 Dec 2009 04:36:20 +0000

Damn it … I want a pair.