Optimizing for Iteration: Choosing Your Early Startup's Tech Stack(monolist.co)
monolist.co
Optimizing for Iteration: Choosing Your Early Startup's Tech Stack
https://monolist.co/blog/2019/09/optimizing-for-iteration-tech-stack/
3 comments
Yup, that's the unfortunate reality you can find yourself in if these things aren't taken into consideration early on.
However, that doesn't mean improvements can never be made. Sounds like it definitely still would've been worth your team learning React!
However, that doesn't mean improvements can never be made. Sounds like it definitely still would've been worth your team learning React!
I worked on a codebase that started as a ASP. NET framework project simply because that's what the team knew. No one knew React, and no one had the impetus to learn it thoroughly, if we forced that requirement we'd have to cut 90% of the team. It's unfortunate because we demonstrated how fast, maintainable, and modular a React-based system could be if developed properly. Multiple high-value features implemented in a single sprint, but as 90% of the team can't use it, we can't implement it everywhere.