3 ms·
As someone who builds reasonably large web apps for a living, this list doesn't really address anything that's specific for large scale. Separation of concerns,
by Etheryte 7y ago
As someone who builds reasonably large web apps for a living, this list doesn't really address anything that's specific for large scale. Separation of concerns, a common API layer, tests, linters and etc are the baseline of good development today, not something to consider only for bigger projects.
What I've dealt with over the years, and would've loved to see addressed, is questions that are actually specific to projects at scale. Having hundreds of views, how do you classify and manage components? How do you manage shared components? How to achieve (and keep) architectural consistency across thousands of components? How do you address death-by-a-thousand-cuts performance regressions in big web apps? And so on. Sadly, this article doesn't address any of these.
- _bxg1 7y agoIt very much comes off as a marketing piece. Heck, the name of the company splashes the page for several seconds before you even see the article. They say some things that aren't really wrong but also aren't really interesting, and it makes them sound like they Really Know What They're Talking About so that you'll pay them to build something for you.