Mv* patterns
•Download as PPTX, PDF•
1 like•2,070 views
This document discusses different software design patterns including MVC, MVP, and MVVM. It notes that all three patterns have the same underlying problems and advocates separating user interface code from other application code. The document recommends practices like dependency inversion, dependency injection, using view models correctly, separating data access code from domain models, and creating your own frameworks tailored to the specific application instead of relying entirely on external frameworks. It emphasizes separating code concerns and not using MVC or other patterns for everything.
Convert to study guideBETA
Transform any presentation into a summarized study guide, highlighting the most important points and key insights.
Mv* patterns
- 1. On MV Whatever frameworks Lessons learned the hard way
- 3. Shot myself in the foot
- 4. What is MVC?
- 5. Model
- 6. View
- 7. Controller
- 9. Model
- 10. View
- 11. Presenter
- 13. Model
- 14. View
- 15. View-Model
- 17. All have the same problems
- 18. For the love of God, why?
- 19. UI, not app patterns
- 21. Separate MVC from all else
- 22. Dependency inversion != Dependency injection
- 26. Learn to use View-Models
- 27. Model != DAL
- 28. Frameworks++++++
- 29. Create your own stuff
- 30. Take aways
- 31. Again, separate your code
- 32. JBITDMYSUI
- 33. Can’t use MVC for everything
- 34. Questions?
- 35. Thank you & Coffee time
Editor's Notes
- #33: Just because it’s there doesn’t mean you should use it