Maintain legacy code: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
Line 21: Line 21:
== further reading ==
== further reading ==
* 王建興 (2009). [http://www.ithome.com.tw/node/57107 如何面對與避免Legacy Code | iThome] 「Michael Feathers曾經對Legacy Code下了另一個定義,他認為Legacy和Non-Legacy Code區分的關鍵,在於測試。」
* 王建興 (2009). [http://www.ithome.com.tw/node/57107 如何面對與避免Legacy Code | iThome] 「Michael Feathers曾經對Legacy Code下了另一個定義,他認為Legacy和Non-Legacy Code區分的關鍵,在於測試。」
* Fukuball Lin (2015). [https://speakerdeck.com/fukuball/indievox-ta-ru-yan-chang-hui-shou-piao-zhi-hou-de-kuai-su-shui-bian-how-we-build-a-scalable-php-website-for-ticketing iNDIEVOX 踏入演唱會售票之後的快速蛻變:How we build a scalable PHP website for ticketing // Speaker Deck]
* zonble (2016). [http://www.slideshare.net/zonble/code-60464624 怎樣寫出比較沒有問題的 Code] 「不要寫 if。如果非要寫 if,不要亂寫 if。」
* zonble (2016). [http://www.slideshare.net/zonble/code-60464624 怎樣寫出比較沒有問題的 Code] 「不要寫 if。如果非要寫 if,不要亂寫 if。」


[[Category:Programming]] [[Category:PHP]]
[[Category:Programming]] [[Category:PHP]]

Revision as of 15:20, 30 June 2016

cases of legacy code

legacy: require_once, include_once

legacy: mysql_query, mysql_fetch_array

legacy: foreach

legacy: nested if-else

  • alternative: interface
(left blank intentionally)
legacy: 
* alternative:

further reading