4 ms·
Good developers are often average designers. And the UI changes are often isolated independent from backend changes. To me, a clean API layer with a static SPA
by guru4consulting 5y ago
Good developers are often average designers. And the UI changes are often isolated independent from backend changes. To me, a clean API layer with a static SPA style frontend makes it much easier to iterate both UI and backend changes in parallel, without risk of one impacting the other. Development, testing and deployments can be separate and be independent of each other. That decoupling enables faster iterations. Sometimes, SSR seems to take us back to the days of JSP/ASP where view generation is tightly coupled with control/backend layer.
- Raidion 5y agoYou're both right. The tradeoff you have to make: is the opportunity cost really worth it? If you're a big company and are greenfielding a new design, you either need a huge amount of buyin (eg we're going to go heads down for 8 months and come up with a solution) OR you need to build something that provides incrimental improvements along the way. It's really hard for a new greenfield system to compete on features with one with 5 years of features on it. If you don't have any users, it's far more valuable to demonstrate the business value as early as possible and then build a more scalable solution that's easier for a large team to manage once you've gotten a good chunk of funding.