Upgrade to Pro — share decks privately, control downloads, hide ads and more …
Sign up for free

Refactoring Re-education

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →
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
100
Rails Girls Chengdu 2014
Avatar for Terry poshboytl
2
340
How we test our projects
Avatar for Terry poshboytl
29
2k

Other Decks in Programming

See All in Programming
月間100万人のサービス刷新で、 技術選定をHonoに振り切った話
Avatar for bara yutobara
8
6.5k
見えないものを探る要求要件定義に必要な基本的思考 / invisible-requirement-thinking
Avatar for MinoDriven minodriven
15
8.4k
モデルのリファクタリングが難しいと思ったら、そもそも複雑だったのはビジネス仕様だった ? / is-the-business-domain-the-real-complexity
Avatar for hatsu hatsu38
0
480
作れる、でも消せるか？──安全に「枯らして消す」機能削除術 / Drain, Then Delete
Avatar for chobishiba chobishiba
2
380
When benchmarks go bad - what I learned from measuring performance wrong
Avatar for Holly Cummins hollycummins
0
210
GemmaをJevのように使ってみる / Use Gemma like Jev
Avatar for Naoki Kishida kishida
5
780
Workers Cache を知る
Avatar for syumai syumai
0
360
AI時代のコードレビューは人に向けるな、仕組みに向けろ
Avatar for meijin texmeijin
5
3.7k
なぜCTOを降りてFDEを選んだのか？〜なぜプロダクト企業がFDEで顧客の現場に踏み込むのか〜
Avatar for ryuta sakamoto gonta
1
200
Everything will be SERVERLESS — 信じて運用した10年の経験値 / Everything Will be Serverless — Lessons Learned from 10 Years of Operational Experience
Avatar for shiro seike seike460
PRO
1
1k
複雑なUIコンポーネントとの ⻑い付き合い⽅：波及するバグからテスト戦略を経て、安全な再設計へ
Avatar for masahiko.asai mixplace
0
400
Compiling a real-world CLI tool to native with Static Hermes
Avatar for Tzvetan Mikov tmikov2023
0
110

Featured

See All Featured
SEO in 2025: How to Prepare for the Future of Search
Avatar for Michael King ipullrank
3
3.9k
The SEO Collaboration Effect
Avatar for Kristina Bergwall kristinabergwall1
1
590
Building the Perfect Custom Keyboard
Avatar for Naoto Takai takai
2
900
Odyssey Design
Avatar for Ryan Kendrick rkendrick25
PRO
2
870
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
Avatar for Mfonobong Umondia mfonobong
2
590
The untapped power of vector embeddings
Avatar for Frank van Dijk frankvandijk
2
1.9k
Data-driven link building: lessons from a $708K investment (BrightonSEO talk)
Avatar for Szymon Słowik szymonslowik
1
1.4k
Side Projects
Avatar for Sacha Greif sachag
456
43k
Are puppies a ranking factor?
Avatar for Jono Alderson jonoalderson
2
4k
How to audit for AI Accessibility on your Front & Back End
Avatar for davetheseo davetheseo
0
600
Code Review Best Practice
Avatar for Trisha Gee trishagee
74
20k
Measuring & Analyzing Core Web Vitals
Avatar for Philip Tellis bluesmoon
9
1k

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!!