| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Coding dojo

Page history last edited by J.P. Hamilton 14 years, 10 months ago

May 7th coding dojo (Registration is Closed)

 

Date: Thursday, May 7th

Time: 6:00PM (coding will begin at 6:30PM sharp)

Venue/location: Microsoft facility (the same room used by HDNUG | directions)

Food/sponsor: Sogeti USA

Focus: Practice Test-Driven Development

Challenge: We will be reusing the theme from Pablo's Days of TDD which occured last October in Austin, TX: User Login

 

This event is at maximum capacity. Registration is closed. was a big success!

 

Overview:

The purpose of a coding dojo is for developers to gather and engage in deliberate practice. Typically, this means working collaboratively to solve a programming challenge. However, coding dojo's need not be limited to coding alone. It is an ideal format for practicing other aspects of our craft, such as Scrum, project planning & estimation, and automated builds.

 

Growing Talent through Coding Dojos

 

Regarding this dojo's focus:

 

Rules of TDD

  1. You are not allowed to write any production code unless it is to make a failing unit test pass.
  2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
  3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.

 

In this dojo we value learning over progress. This means that you will have to willingly work below your 'natural' speed in order to adhere to our strict version of TDD.

 

How this works:

If interested, read this transcript of Uncle Bob Martin's implementation of bowling scores.

  • Two developers (pilot and co-pilot) pair at the keyboard:
    • They write a test.
    • They do the absolute minimum to get the test to compile.
    • They verify that the test they have just written fails.
    • They write the absolute minimum code necessary to get the test to pass (remember rule of TDD #3 above), "committing many sins along the way." Absolute minimum means even hard-coding return values! 
    • They refactor.
    • They verify that the test still passes.
    • Co-pilot becomes the pilot, and a new co-pilot takes his place.
  • Near the end of the session we stop coding and have a retrospective.

 

Preparing yourself for this dojo:

  • Please bring a laptop!
    • Visual Studio 2008
    • NUnit 2.4.x
  • We will be coding in C#, and ask that if you participate, you feel comfortable coding in C#.
    • We do not require knowledge of a specific UI framework (e.g. WinForms/ASP.NET/WPF/Silverlight/WinMo).
  • NUnit: We will be using NUnit. We do not require prior knowledge of NUnit. If you'd like to become more comfortable, watch some of these short screencasts
  • We do not require prior experience with TDD. Here are some good resources you may want to read to familiarize yourself with the basics:

 

Acknowledging the intimidation factor

 

We understand that coding in public is intimidating and will make every effort to keep this dojo a safe, fun environment. You do not have to participate in the dojo (i.e. sit at the keyboard and code in front of others) if you don't wish.

 

Retrospective

Comments (0)

You don't have permission to comment on this page.