We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
No, because you write the code. If you follow framework guidelines and such, then you end up in a better place than most ppl. But most typically people will just do whatever they want. (two examples: MVC/MVVM pattern. Lots of framework, but ppl still get it wrong. Other one is react's useEffect. It is getting so much abuse, and yet people keep doing it) so TLDR: no. #IMO
No, the frameworks you mentioned just provide the MVVM data-driven architecture with some state management pattern. The rest is anything but strict. (Angular is a bit stricter, and its CLI promotes good practices, but one can still bend it to your will very easily.) One can still stuff all your business logic, UI state, and data fetching stuff into one component, one function, or even better, scatter them into template bindings. Once a 2000-line component file got created, adding features for new business requirements or refactoring becomes a PITA. Frameworks don't help you achieve better abstractions and modularity. That's all.
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
What is the book Simon refers to at 09:16?
I'm guessing it's Rational Unified Process, Third Edition (RUPTH)
Awesome talk!
What about frameworks, are they already force us to be in a strict architecture, Flux, Vue/pinia, React/Mobx?
No, because you write the code. If you follow framework guidelines and such, then you end up in a better place than most ppl. But most typically people will just do whatever they want. (two examples: MVC/MVVM pattern. Lots of framework, but ppl still get it wrong. Other one is react's useEffect. It is getting so much abuse, and yet people keep doing it) so TLDR: no. #IMO
No, the frameworks you mentioned just provide the MVVM data-driven architecture with some state management pattern. The rest is anything but strict. (Angular is a bit stricter, and its CLI promotes good practices, but one can still bend it to your will very easily.) One can still stuff all your business logic, UI state, and data fetching stuff into one component, one function, or even better, scatter them into template bindings. Once a 2000-line component file got created, adding features for new business requirements or refactoring becomes a PITA.
Frameworks don't help you achieve better abstractions and modularity. That's all.
UML, I have a guy that that wants everything in a sequence diagram. It’s soo 1995.
Sure that the architect needs soft skills first. One must make an impression that long general talks, top diagrams are of any value.