mind map: https://coggle.it/diagram/WAHeC68sAvMFMJtP 程式設計不等於軟體開發！優化個人、團隊的開發環境，減少失誤，提升工作效率。綜觀原始人到現代人是如何寫程式，到 Extreme Programming 跟 DevOps 的誕生，如何跟大家協同開發，並期許自己不要成為豬一般的隊友

1. Maxis Kao | Oct. 19, 2016
> 優化開發環境 無料提升戰⾾鬥⼒力

2. Maxis Kao
➔ Software Engineer at Yahoo
➔ Top Hack of Yahoo TW/JP Joint Hackday
➔ Winner of Yahoo Bot Challenge

5. 範疇

7. 環境決定論

8. ⼯工程師⽣生態系

9. ⾓角⾊色 / 需求
• RD：程式
• PM：時程
• Company：成本 + ⾵風險
• Client：產品

10. 原始⼈人寫程式

11. 很久很久以前
• PM：明天新功能上線！
• RD 1：⼤大部份都做好了，等等跟 RD 2 合併
• RD 2：我只差剩下的⼀一些⼩小 bug 待會修⼀一下就好
• QA：看起來還⾏行，但疑似有些 bug 無法重現 (reproduce)
• PM：沒關係，晚上衝⼀一下！明天開⼼心上線

12. 半夜 12 點

13. RD
• RD 1：我們來合⼀一下 code
[ 經過漫⻑⾧長的半⼩小時，解 conflict ]
• RD 2：奇怪為什麼我的電腦上有錯你的沒有
• RD 1：等等！我現在⼜又跑出奇怪的 bug，先來速速解⼀一下

14. QA
• 之前壞掉的好像修好了
• 原本好的貌似變得不穩定
• 到底什麼時候可以給我最終版

15. PM
• 什麼？！剛剛不是說快弄好了
• 乖乖
• 踱步
• 抓頭

16. 早上 7 點

17. 上線

18. 悲劇

19. 現代⼈人寫程式

20. “什麼是環境?”

23. ⼯工作環境 開發環境 開發流程

24. ⼯工作環境

25. M A C B O O K P R O
蘋 果
I P H O N E
寫 很 滿 的 筆 記 本
搖 滾 樂 + 莫 扎 特
便 宜 的 咖 啡
在 講 設 計 的 書
很 普 通 的 鉛 筆
⼤大 桌 ⼦子
密 密 ⿇麻 ⿇麻 像 駭 客 ⼀一 樣
I K E A 的 檯 燈

26. 開發環境 / ⼯工具

27. 開發環境
• OS
• Text editors
• Command line tools
• Web Platform

28. OS
• Windows
• Linux
• Mac
OS
• Ubuntu
• Debian

29. Text editors
• Notepad

30. Text editors
• Notepad
• Sublime
Text

31. Text editors
• Notepad
• Sublime
Text
• vim
• emacs

32. Command line tools
• ZSH
(oh-­‐my-­‐zsh)

33. Command line tools
• ZSH
(oh-­‐my-­‐zsh)
• tmux
+
htop

34. Web platform as a service
• AWS
• Heroku
• Google
App
Engine

35. 開發環境 / 流程

36. 程式設計 ≠ 軟體開發

37. 個⼈人開發環境
⼤大⼈人不在家，怎麼做都開⼼心

38. 團隊開發流程
⾃自⼰己亂寫就算了，但要為別⼈人設想

39. “10+ Deploys per Day
Dev and Ops Cooperation at flickr”
- John Allspaw and Paul Hammond

40. Patrick DeBois
#devops

41. #devops
since 2009

43. – 蔣渭⽔水
“同胞須團結，團結真有⼒力”

44. 在 DevOps 出現之前...

45. – an angry ops guy
“It’s not my machines,
it’s your code!”

46. – an angry dev guy
“It’s not my code,
it’s your machines!”

47. Dev Ops
改變 穩定

48. Dev Ops
改變 穩定

49. DevOps key points
• automated infrastructure (⾃自動化集成)
• shared version control (共⽤用程式碼)
• one step build and deploy (持續建構/部署)
• feature flags (主幹開發)
• shared metrics (不藏私)
• IRC and IM robots (信息整合)

50. A survey
• 來源: RightScale
• 受訪者: 1,060 資訊⼈人員
• 42% 就職於超個 1,000 ⼈人的⼤大公司

56. “XP”

58. “Extreme Programming”
- Kent Beck since 1996

59. YAHOO!+
企業經驗

60. Extreme Programming
• Fine-scale feedback (細微回饋)
• Continuous process (持續程式)
• Shared understanding (共識)
• Programmer welfare (⼯工程師的利益)

61. Fine-scale feedback (細微回饋)
• Whole team
• Test-driven development (TDD)
• Planning game
• Pair programming

62. Fine-scale feedback (細微回饋)
• Whole team
• Test-driven development (TDD)
• Planning game
• Pair programming

63. Dev ⬄ Client

64. Fine-scale feedback (細微回饋)
• Whole team
• Test-driven development (TDD)
• Planning game
• Pair programming

65. 先寫測試！
先寫測試！
先寫測試！

66. test environments &
frameworks

67. Fine-scale feedback (細微回饋)
• Whole team
• Test-driven development (TDD)
• Planning game (策劃遊戲)
• Pair programming

68. Exploration phase
• Write a Story
• Estimate a Story
• Split a Story

69. Commitment phase
• Sort by Value
• Sort by Risk
• Set Velocity
• Choose scope

70. Steering phase
• 估計誤差
• 客⼾戶需求改變

71. Fine-scale feedback (細微回饋)
• Whole team
• Test-driven development (TDD)
• Planning game
• Pair programming (⼀一起寫扣)

73. “Is pair programming worth it?”

74. Continuous process (持續程式)
• Small releases
• Continuous integration
• Design improvement

75. Continuous process (持續程式)
• Small releases
• Continuous integration
• Design improvement

77. Continuous process (持續程式)
• Small releases
• Continuous integration (持續整合)
• Design improvement

78. – Standard Bank: Our DevOps Journey
“The Chop Chop team”

79. Dawie (CIO) + Dev + Ops
War Room !

80. 2000 x
軟體交付速度的破壞性變⾰革

81. – Marissa Mayer
“沒有持續交付 (Continuous Delivery)
專案不得上線，我不是在說笑”

82. 100%
Continuous Delivery

83. – SJ Chou, Senior Engineer at Foxconn
“有事沒事就把⼤大家寫的 code 合起來
跑看看有沒有錯”
持續 整合

84. – SJ Chou, Senior Engineer at Foxconn
“有事沒事就把⼤大家寫的 code 合起來
跑看看有沒有錯”
持續 整合

85. – SJ Chou, Senior Engineer at Foxconn
“有事沒事就把⼤大家寫的 code 合起來
跑看看有沒有錯”
持續 整合

86. 天下武功 無堅不破 唯快不破

89. Continuous process (持續程式)
• Small releases
• Continuous integration
• Design improvement

90. “Refactoring”
Improving the Design of Existing Code

91. Refactoring: Improving the
Design of Existing Code
Martin Fowler

92. Refactoring ⬄ Users

93. Refactoring
is
boring.

94. ok, but how?

96. “Bad Smells”

97. Long Parameter List.
Divergent Change.
Shotgun Surgery.
Feature Envy.
Data Clumps.
Primitive Obsession.
Switch Statements.
Parallel Inheritance Hierarchies.
Lazy Class.
Speculative Generality.
Temporary Field.
Message Chains.
Middle Man.
Inappropriate Intimacy.
Alternative Classes with Different Interfaces.
Incomplete Library Class.

98. Bad smells
• Duplicated Code
• Long Method / Large Class
• Long Parameter List
• Switch Statements
• Indecent Exposure
• Feature Envy
• Comments

99. Duplicated Code
• 恐怖份⼦子⾸首腦
• Don't Repeat Yourself!

100. Long Method / Large Class
• ⼀一個 main() 上萬⾏行
• 負擔過多責任
• Extract Class / Subclass / Interface

101. Long Parameter List
• Hard to understand
• Inconsistent
• set
(a,
b,
c,
x,
y,
z,
flag,
amount)
• set
(a,
b,
c,
y,
x,
z,
flag,
amount)

102. Switch Statements
• 「好的物件導向程式應該少⽤用 switch」
• open-closed principle (OCP)

103. Indecent Exposure
• 家⾨門要記得關，沒必要的東⻄西不要隨便 public

104. Feature Envy
• 特性依戀

105. Comments
/*
*
This
is
a
add
function,
returns
a
+
b
*/
function
kerker
(a,
b){
return
a
+
b;
}

106. Comments
/*
*
Returns
a
+
b
*/
function
add
(a,
b){
return
a
+
b;
}

107. @use JSDoc

109. Shared understanding (共識)
• Simple design
• System metaphor
• Coding standard
• Collective code ownership

110. Shared understanding (共識)
• Simple design
• System metaphor
• Coding standard
• Collective code ownership

111. Shared understanding (共識)
• Simple design
• System metaphor
• Coding standard
• Collective code ownership

112. Shared understanding (共識)
• Simple design
• System metaphor
• Coding standard
• Collective code ownership

113. long_function_name
vs
longFunctionName

114. Shared understanding (共識)
• Simple design
• System metaphor
• Coding standard
• Collective code ownership

115. – SJ Chou, Senior Engineer at Foxconn
“有事沒事就把⼤大家寫的 code 合起來
跑看看有沒有錯”
持續 整合

116. version control
• 根據定義，可以⽤用以下 check list 判斷是否 version control
Version Control check list:
[ ] record changes over time
[ ] recall a specific version

117. version control
• 根據定義，可以⽤用以下 check list 判斷是否 version control
Version Control check list:
[v] record changes over time
[v] recall a specific version

118. “collective”

119. version control systems

120. Git ≠ Github

121. Git flow
A successful Git branching model
Vincent Driessen

122. 2 main + 3 supporting branches

123. main branches
• develop
• master

124. supporting branches
• feature
• release
• hotfix

125. Commit Messages

126. * fde679b
-­‐
very
hot
fix
<allen>
* d0ad381
-­‐
Kerker.
<maxis>
* f007579
-­‐
test
<jason>
* 09b9813
-­‐
fix
bug.
<maxis>
* 2430918
-­‐
fix
bugs
<allen>
* fde679b
-­‐
abc123
<jason>
* b6c7ee1
-­‐
hot
fix
<allen>

128. 7 rules of a great commit message
• Separate subject from body with a blank line
• Limit the subject line to 50 characters
• Capitalize the subject line
• Do not end the subject line with a period
• Use the imperative mood in the subject line
• Wrap the body at 72 characters
• Use the body to explain what and why vs. how

129. * fde679b
-­‐
Fix
typo
in
the
Search
Box
<allen>
* d0ad381
-­‐
Revamp
Search
Box
UI
<maxis>
* f007579
-­‐
Add
new
Search
Box
UI
<jason>
* 09b9813
-­‐
fix
bug.
<maxis>
* 2430918
-­‐
fix
bugs
<allen>
* fde679b
-­‐
abc123
<jason>
* b6c7ee1
-­‐
hot
fix
<allen>

131. Programmer welfare (⼯工程師的利益)
• Sustainable pace

132. “40-Hour Work Week”

133. 雅⻁虎經驗

134. • Training - Ninja Kata
• DevOps - Docker
• CI/CD - Jenkins

135. – Peter Drucker
“Do the right thing”

136. Thanks :P

137. Q / A

138. 可以這樣找到我
• Maxis Kao
• maxis1718@gmail.com
• http://maxis1718.github.io