Pairing, fast and slow

Hello

PAIRING,FAST and SLOW

i18n蘇泰安 f taiansu

README.mdaboutćmeftaiansu

logdo Ŷćyear 電腦雜誌技術編輯 endgem install railsvalidates čhaveYscjp Ṡẞ truemvim jćrbĉ jćjsworkYat OptimisDevrfronYend j ẄćỶ Ś backYend j ẄćŶ

What is pair programming

Two programmers at one computerOne drivesċ the other navigatesSwitching roles fluidlyThey constantly communicate

Why Pairing

Ỳć reduction in defect rates of ỲẎỜ to ẎẄỜÝć better designĉ simplerĉ moreQmaintainable codeŶć impossible problems become easy or even quick

Way more fun then it sounds

productivity && fun

Ninja( feel like )

Herbert Simon:I 情境提供了線索ĉ

線索讓專家得以提取記憶中的訊息ĉ而訊息提供了答案。

專家直覺就是辨識，不多也不少，就是它。 J

Two system

System 1automaticllyquicklylittle or no effortno sense of voluntart control

17 * 24

CPU bound

Pay attention

System 2conscious and resoningallocates attentionslowhave boundrylazyĉ lazyĉ lazy

Cache things to System 1

system_1 += system_2take 10,000 hours

Müller Lyer illusion

Think pair programmingthis way

The driverfocuses on tactics:

writing clean code that runs and pass the testć

The navigatorfocuses on strategy:

how the code fits into the overall designwhich tests will drive the code forwardwhich refactorings will improve the entire codebase

Our Case

Goal

Discuss

& Code

What we found

Set up a goal everytime

TDD is great for pairing

Stay talking

shared knowledgeboth technique

and your application

You'll know your partner more

improve communicationability

rest frequently

Result

3 days30 LOC

plus test

U no pair?

Office settingBoss

Culture

ToolsScreenHero with Skypetmux

It's an insurance

名為'信賴'的模型

martz 松本行弘的程式世界, 2009

I 但是，從前面的的討論也能發現，會發生這些問題的「大規模開發」，

顯然也不是什麼幸福的狀況。

是不是應該先改善專案內的信賴關係，直到足以採用Ruby的程度為止。就算最後決定不使用Ruby也一樣 J

Fear

How to doOEREILLYč The Art of Agileĉ Chć ẎćỲ

How they doPeepCodeč play by play series

bitćlyfWbAÝbH

Thank youany questions?