lot of decisions that go into building a high-performance web application. • How to fetch data • How to render your application • Dealing with user interaction Is it worth solving these problems more than once?
shifts are easy to justify ◦ Vanilla -> jQuery -> Backbone -> React • What determines a paradigm shift? ◦ Does it change how you think and develop your product? • Lateral movements are usually not worth it. ◦ Switching between different flavors of Flux
them out. ◦ Ensure you have a rollback plan in place. • Optimize for fewer breaking changes. ◦ Stopping the world is very expensive. ◦ Incremental adoption ensures that you’re always in a working state.
Way™ Moving between teams is like moving between states, not moving between countries. Most of the problems you’re solving are generalizable anyway. Improvements can be shared across your whole organization.
These sorts of decisions are already being made implicitly throughout your organization. • Have a North Star to guide your development ◦ Having an opinion is different than knowing what you care about.