Download to read offline
Uploaded byIvan Nemytchenko
Principles. Misunderstood. Applied
The document discusses software development principles, notably within the context of Ruby on Rails, emphasizing concepts like DRY (Don't Repeat Yourself), KISS (Keep It Simple, Stupid), and YAGNI (You Aren't Gonna Need It). It critiques the common misapplication of these principles, suggesting that Rails can create complex problems rather than simplify them, and encourages developers to rethink traditional MVC structures. The author advocates for principles like composition over inheritance and suggests exploring alternative architectural paradigms.
Principles. Misunderstood. Applied
- 1.
- 2. ▸ phyzfack ▸ 3years in webdev companies ▸ freelance on rails ▸ company of 4 ▸ company of 15 ▸ back to development
- 3.
- 4. ▸ DRY -"Do not repeat yourself" ▸ KISS - "Keep it simple, stupid" ▸ Convention over configuration ▸ Fat model, skinny controller ▸ Rails is not your application ▸ YAGNI - "You aren't gonna need it" ▸ Prefer composition over inheritance
- 5. DRY "DO NOT REPEATYOURSELF"
- 6.
- 8.
- 9.
- 10. DRY PRINCIPLE ATTHE EARLY STAGES
- 12. Duplication is muchcheaper than wrong abstraction — Sandi Metz
- 13. KISS "KEEP IT SIMPLE,STUPID"
- 14.
- 15. RAILS WORLD ISSO COOL, THAT WE DON'T EVEN HAVE WHOLE CLASS OF PROBLEMS, WHICH MILLIONS OF JAVA PROGRAMMERS STRUGGLING EVERY DAY!
- 16.
- 17. ▸ input datacoercion ▸ setting default values ▸ input data validations ▸ interaction with the database ▸ handling nested structures ▸ callbacks(before_save, etc...)
- 18. BUT WHY SHOULDI CARE?
- 19. Polymorphic STI modelwhich belongs to another polymorphic model through another model, which also has some valuable JSON data stored in Postgres using hstore
- 20. WHAT ARE YOUGONNA DO? ▸ reorganize your associations & app ▸ become Rails contributor
- 21. IT IS GOINGTO BE PAINFUL
- 22. PAINFUL BECAUSE OFTHE COMPLEXITY
- 23. RAILS IS NOTSIMPLE, IT IS CONVENIENT.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31. BUT IT ISPART OF THE PROBLEM
- 32. YOU SHOULD HAVENO FAT CLASSES AT ALL
- 33. PROPER SOLUTION REQUIRES THINKING OUTOF MVC BOX
- 34. RAILS IS NOTYOUR APPLICATION
- 35. IT JUST DOESN'TMAKE SENSE. HERE'S MY RAILS APPLICATION. HERE'S app FOLDER. WHAT'S WRONG?
- 38. Many developers aretrying to fit business logic into MVC design pattern
- 39. But MVC isonly for how we're going to serve stuff to the web
- 40. P.S. GOOGLE FOR: ▸Clean architecture ▸ Hexagonal architecture
- 43. YAGNI "YOU AREN'T GONNANEED IT"
- 44. WHAT IF INYOUR APPLICATION DON'T NEED PERSISTANCE YET?
- 45. WHAT IF INYOUR APPLICATION DON'T NEED WEB FRAMEWORK YET?
- 46.
- 49. Question everything generally thoughtto be obvious. — Dieter Rams
- 50.