Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Refactoring Re-education

Avatar for Terry Terry
February 25, 2013
Programming
990
5

Refactoring Re-education

Summarize the work for refactoring Re-education project.

Avatar for Terry

Terry

February 25, 2013

More Decks by Terry

See All by Terry
Building API For The REST of Us
Avatar for Terry poshboytl
8
750
RubyConf China Welcome Slides
Avatar for Terry poshboytl
1
96
Rails Girls Chengdu 2014
Avatar for Terry poshboytl
2
340
How we test our projects
Avatar for Terry poshboytl
29
1.9k

Other Decks in Programming

See All in Programming
Claude Team Plan導入・ガイド
Avatar for tk3fftk tk3fftk
0
220
JAWS-UG横浜 #102 AWSサ終供養LT会 成仏できない AWS サービスたち 〜本日、三体供養します〜
Avatar for maroon1st maroon1st
0
220
なぜ型を書くのか？ TSKaigi2026で改めて考える #tskaigi_smarthr
Avatar for Takuma Kajikawa kajitack
0
400
エンジニア向け会社紹介/Findy Company Profile
Avatar for Findy findyinc
6
360k
AI がコードを書く時代における新卒エンジニアの仕事風景 (2026) / New Graduate Engineers in the Era of AI Coding (2026)
Avatar for sushichan044 sushichan044
0
230
信頼性について考えてみる（SRE NEXT 2026 miniLT）
Avatar for hayama hayama17
0
200
AI駆動開発を妨げる技術的負債の解消アプローチ / ai-refactoring-approach
Avatar for MinoDriven minodriven
17
9.2k
yield再入門 #phpcon
Avatar for hideki kinjyo o0h
PRO
0
700
初めてのKubernetes 本番運用でハマった話
Avatar for Kobujee_53 oku053
0
130
ルールを書いて終わらせないハーネスエンジニアリング
Avatar for Yuji Yamaguchi yug1224
4
1.7k
【SRE NEXT 2026 Lunch Session】一人目専任SREの立ち上げを加速する ― AIと進めたオンボーディングで2分を0.04秒にした話
Avatar for PKSHA Technology（パークシャテクノロジー） pkshadeck
PRO
0
2.9k
なぜ関数型プログラミングで「型」と「証明」が語られるのか #fp_matsuri
Avatar for Takuma Kajikawa kajitack
3
1k

Featured

See All Featured
Automating Front-end Workflow
Avatar for Addy Osmani addyosmani
1370
210k
Thoughts on Productivity
Avatar for Jon Yablonski jonyablonski
76
5.3k
What the history of the web can teach us about the future of AI
Avatar for Ines Montani inesmontani
PRO
1
640
Hiding What from Whom? A Critical Review of the History of Programming languages for Music
Avatar for Tomoya Matsuura tomoyanonymous
3
1k
Groundhog Day: Seeking Process in Gaming for Health
Avatar for Sebastian Deterding codingconduct
0
250
コードの90%をAIが書く世界で何が待っているのか / What awaits us in a world where 90% of the code is written by AI
Avatar for r-kagaya rkaga
62
45k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
Avatar for Stéphanie Walter stephaniewalter
287
14k
The untapped power of vector embeddings
Avatar for Frank van Dijk frankvandijk
2
1.8k
Jess Joyce - The Pitfalls of Following Frameworks
Avatar for Tech SEO Connect techseoconnect
PRO
1
310
ピンチをチャンスに：未来をつくるプロダクトロードマップ #pmconf2020
Avatar for Aki / @LoveIdahoBurger aki_iinuma
128
56k
The World Runs on Bad Software
Avatar for Brandon Keepers bkeepers
PRO
72
12k
The agentic SEO stack - context over prompts
Avatar for schlessera schlessera
0
850

Transcript

  1. Refactoring re-education Terry Tai

  2. who am i

  3. 太檑

  4. Terry

  5. @poshboytl

  6. Co-founder of Pragmatic.ly

  7. None

  8. Creator of railscasts-china.com

  9. None

  10. What refactoring is

  11. Refactoring is improving the design of codes without changing it’s

    behaviour.

  12. How to begin

  13. Run tests

  14. How about if there is no test

  15. Write integration tests to protect the user heavier

  16. Unit tests might be change when doing refactor

  17. I choose Rspec/Capybara

  18. Code Conventions

  19. Use spaces instead of tabs

  20. None
  21. None

  22. Do not use unless ... else...

  23. None

  24. Don’t require things several times

  25. None

  26. Conventions might be different in different teams

  27. Code design

  28. None
  29. None

  30. Put filter method in private/protected

  31. None
  32. None

  33. Slim controllers Fat models

  34. None
  35. None
  36. None
  37. None
  38. None

  39. Refactor in your daily work

  40. Write tests

  41. It’s better if you do TDD

  42. Pair with your friends sometimes

  43. Almost never push codes to master straightly

  44. Create branch for every ticket

  45. Send Pull Request And do code review

  46. Make sure running tests before you push

  47. Treat every piece of your codes as open source codes

  48. About README • Explain why your code exists. • Tell

    people how to use it • Declare copyright and licensing • Describe how to conribute

  49. Keep Rocking!!