Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

BJSS Code Dojo - Kata Potter

No description

Grant Crofton

on 21 August 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of BJSS Code Dojo - Kata Potter

BJSS Code Dojo Purpose Self-Improvement through Deliberate Practice Use considered techniques Try different aproaches Functional Different Language Pair Programming Energised working Less defects No code review Techniques Pair Programming Test Driven Development Pairing Methods Time boxed - e.g. 5 mins each One writes test, other makes it pass One writes a test and makes it pass Point is not to code a solution Kata Potter New Requirements! Other techniques are available! Master IDE Test Driven Development Tests drive code design Small, incremental changes Not about testing! Tight feedback loop TDD Steps Red Green Refactor Write failing test Small step! Make test pass Simple code Only existing tests! Red Green Refactor Remove duplication Code quality Tests & code (one at a time!) Schedule 18:30 - Introductions 18:45 - About Code Dojo 19:00 - Start Coding! 20:45 - Retrospective 5 Books, £7.00 each 21:00 - Drinks & socialising.. More New Requirements!!! Uncle Bob's Rules of TDD You may not write production code until you have written a *failing* unit test. You may not write more of a unit test than is sufficient to fail. You may not write more production code than is sufficient to pass the current failing test. Code Example
Full transcript