Code Dojo

CODEDOJO

@cakper

17/06/13 Gdańskcode dojo

@CAKPER

Software Engineer @SensioLabsUKSilesia PHP User Group // Spug.pl#symfony-pl // Symfonylab.pl

flickr.com/foliosus/2792686705/

道場Dojo


“PLACE OF THE WAY”


DELIBERATE PRACTICE

“Done on purpose; inten.onal.

Formed with delibera.on; well-‐advised; carefully considered; not sudden or rash.

Not hasty or sudden; slow.”

http://en.wiktionary.org/wiki/purpose

http://en.wiktionary.org/wiki/purpose

http://en.wiktionary.org/wiki/intentional

http://en.wiktionary.org/wiki/intentional

http://en.wiktionary.org/wiki/sudden


http://en.wiktionary.org/wiki/rash

http://en.wiktionary.org/wiki/rash

http://en.wiktionary.org/wiki/hasty

http://en.wiktionary.org/wiki/hasty




DELIBERATE PRACTICE

10 000Hours


DELIBERATE PRACTICE

practice must: be focussed be goal-directed stretch your abilities give continuous feedback be followed by self-reflection

@sleepyfox


DREYFUS MODEL OF SKILL ACQUISITION

Novice

Advanced beginner

Proficient

Competent

Expert

flickr.com/kaibara/1449448184/

型

KAta


“FORM”

CODE KATA


Dave ThomAs


CODE KATA

Time to improve skillsFocus on process, not resultsPracticeRepetitionTDD


CODE KATA

uninterruptedchallengingNo PressureMistakes are goodSmall steps


KATA IDEAS

String CalculatorCode breakerArgument ParserBowling GameNumber NamesFizz Buzz


KATA IDEAS

http://codekata.pragprog.com/codekata/

http://www.wiredtothemoon.com/2012/12/12-tdds-of-christmas/









TEST DRIVEN DEVELOPMENT



TDD CYCLE

RED

GREENREFACTOR


3 LAWS OF TDD

1.Don’t write any code unless you are making a failing test pass

2.Don’t add to the test more than enough to get a failure

3.Only write enough code to make the one failing test pass


4 RULES OF SIMPLE DESING

1.All the tests pass.

2.Express every idea we need to express.

3.Contains no duplication.

4.minimize the number of classes, methods and other moving parts.

PAIR PROGRAMMING



PAIR PROGRAMMING

Navigator&

Observer


PAIR PROGRAMMING

Knowledge FlowReduction of defectsBetter designimproved disciplineBetter Time managementConfidence


TDD PING PONG

First Person writes a testSecond writes an implementationboth refactorSecond Person writes next testIterate

BE ORGANISED



CODE CLUB

Choose your kata Set session time // 3*20 minutesPair programmingDelete code after each sessionSwap with Partner


CODE RETREAT

Day-Long session // 4*1 hourDiscuss what happenedProblem is more complex Example: Game-of-life


CODE DOJO

Choose your kata ONE ProjectorONE IDEONe PairSensei Guides the sessionLearn from the groupSwap every N-Minutes

TOOLS MATTER



TOOLS MATTER

LanguageIDETesting FrameworkMocking FrameworkRefactoring tools


TOOLS MATTER

BUT CHALLENGE YOURSELFAND TRY SOMETHING NEW


KATA CONSTRAINTS

Method length limitNo MouseNo loopsNo If/else/switch statementsRefactor at least 3 times No state

“It's not practice that makes it perfect. It's

perfect practice”



Questions?


WE ARE HIRING!

Software EngineerFront-end EngineerSoftware Engineer in testPRoject managerBusiness analyst

www.sensiolabs.co.ukwww.inviqa.com

http://www.sensiolabs.co.uk/

http://www.sensiolabs.co.uk/

http://inviqa.com/

http://inviqa.com/

THANK YOU!

@cakper

Technology

Code Dojo