+ All Categories
Home > Documents > Coding Dojo

Coding Dojo

Date post: 22-Feb-2016
Category:
Upload: hue
View: 52 times
Download: 0 times
Share this document with a friend
Description:
Coding Dojo. AgilePrague 2012 Johannes Brodwall , Principal Architect Steria Norway @ jhannes. Prague Coding Dojo ? http://johannesbrodwall.com/2011/12/18/how-to-start-a-coding-dojo/. Motivation. Master programming. through practice. What does good programming mean for you ?. - PowerPoint PPT Presentation
55
Coding Dojo AgilePrague 2012 Johannes Brodwall, Principal Architect Steria Norway @jhannes
Transcript
Page 1: Coding Dojo

Coding DojoAgilePrague 2012

Johannes Brodwall, Principal ArchitectSteria Norway

@jhannes

Page 2: Coding Dojo
Page 3: Coding Dojo
Page 4: Coding Dojo
Page 5: Coding Dojo
Page 6: Coding Dojo

Prague Coding Dojo?http://johannesbrodwall.com/2011/12/18/how-to-start-a-coding-dojo/

Page 7: Coding Dojo

Motivation

Page 8: Coding Dojo

Master programming

Page 9: Coding Dojo

through practice

Page 10: Coding Dojo

What does good programming mean for you?

How do you want to apply this tomorrow?

What do you want to get out of the day?

Page 11: Coding Dojo

Agenda

Page 12: Coding Dojo

• 9:10: Demo of TDD and pair programming• 9:20: Randori style Leap Years kata with everyone• 9:40: Paired style Prime Factors• 10:10: Retrospective• 10:30: Paired style Prime Factors, take 2• 11:00: Coding dojo 2:

Romans if you’re slow,Yahtzee if you’re quick,minesweeper if you’re smart

• 12:00: Retrospective• 12:15: Lunch (?)• 13:00: Extreme startup – first round• 13:30: Break• 13:45: Extreme startup – second round• 15:45: Wrap-up

Page 13: Coding Dojo

TDD

Page 14: Coding Dojo

TDDNo code without test

Just enough test to redJust enough code to green

(+ refactor!)

Page 15: Coding Dojo

Pair programming

Page 16: Coding Dojo

Ping/pongDriver/Navigator

Page 17: Coding Dojo

Failing test

Write code

Failing test

Write code

Failing test

Page 18: Coding Dojo

Failing test

Write code

Failing testWrite code

Failing test

Refactor code and tests

Refactor code and tests

Page 19: Coding Dojo

What benefits can you get from pair programming?

Page 20: Coding Dojo

Kata 0: Leap Year

Page 21: Coding Dojo

Kata 1: Prime factors

Page 22: Coding Dojo

Kata: Prime factors1 => []

2 => [2]3 => [3]

4 => [2,2]…

2*2*13*17*23*23 => [2,2,13,17,23,23]

Page 23: Coding Dojo

Did you change drivers at good frequency?

How did the solution end up looking?

How did you determine next test?

What tests did you start with?

Which tests didn’t help you?

How did your choice of language help/hurt?

Page 24: Coding Dojo

What surprised you?

What do you want to achieve next round?

What did you learn?

Page 25: Coding Dojo

Kata 2a: Minesweeper

Page 26: Coding Dojo

Given:var minefield = new Minefield([ "....", ".*..", ".*.*", "...*“ ])

Page 27: Coding Dojo
Page 28: Coding Dojo

What surprised you?

What do you want to achieve next round?

What did you learn?

Page 29: Coding Dojo

Did you change drivers at good frequency?

How did the boundary conditions affect your test and code?

How did you determine next test?

What tests did you start with?

Which tests didn’t help you?

How did your choice of language help/hurt?

Page 30: Coding Dojo

Kata 2b: Yahtzee

Page 31: Coding Dojo

Kata: Yahtzee({1,1,1,1,1}, «ones»} => 5({1,1,1,1,1}, «sixes»} => 0

({1,1,1,1,1}, «yahtzee»} => 50

Ones, twos, threes, fours, fives, sixesPair, two pairs, three of a kind, four of a kind, full house

YahtzeeLittle straight, big straight

Chance

Page 32: Coding Dojo

What surprised you?

What do you want to achieve next round?

What did you learn?

Page 33: Coding Dojo

Did you change drivers at good frequency?

What is ({2,2,3,6,6}, «pair»)?

How did you determine next test?

What tests did you start with?

Which tests didn’t help you?

How did your choice of language help/hurt?

Page 34: Coding Dojo

Kata 2c: Romans

Page 35: Coding Dojo

Kata: Romans1 => I

5 => V1999 => MCMXCIX

Page 36: Coding Dojo

What surprised you?

What do you want to achieve next round?

What did you learn?

Page 37: Coding Dojo

Did you change drivers at good frequency?

How did you implement rules for «IV» etc?

How did you determine next test?

What tests did you start with?

Which tests didn’t help you?

How did your choice of language help/hurt?

Page 38: Coding Dojo

Extreme startup

Page 39: Coding Dojo

The Extreme startup code competition

By Matt Wynne and Robert Chatly

Page 41: Coding Dojo

RulesCheat like mad!

Only results matterNo destruction of property

Obey local lawsDon’t f$%! with workshop computer

Page 42: Coding Dojo

GuidelinesWork as you like

(Tip: Use a language you know)Help those behind

Upload your code (if possible)

Page 43: Coding Dojo

OrientationDownload starting point

(http://github.com/steria/extreme_startup_servers)

Start serverRegister

(http://192.168.155.249:3000/)

Solve questions

Page 44: Coding Dojo

Form teams!

Page 45: Coding Dojo

Round 1

Page 46: Coding Dojo

Round 1(fight!)

Page 47: Coding Dojo

Round 1: Retrospective

Page 48: Coding Dojo

What surprised you?

What do you want to achieve next round?

What did you learn?

Page 49: Coding Dojo

Round 2

Page 50: Coding Dojo

Round 2(fight!)

Page 51: Coding Dojo

Round 2: Retrospective

Page 52: Coding Dojo

CourseRetrospective

Page 53: Coding Dojo

What surprised you?

How will you change how you work?

What did you learn?

Page 54: Coding Dojo

Testing?

Teamwork?

Which questions did you solve?

Annoying questions?

How did you mess up?

How did you cheat?


Recommended