Principles of scalable front end projects
The article does not mention what the author means by “scaleable” projects. Scaleable in terms of the codebase being used by tens or hundreds of apps? Scaleable in terms of tens or hundreds of developers working in the same codebase? Scaleable in terms of millions of users with different hardware and devices using the web sites?<p>My guess is that it is “scaleable in terms of a team of 10-20 developers working on the same codebase”.
The practices are fair in this sense, though I’m a bit unsure on the specific library recommendations and why they are better than the alternatives not listed. I was also missing things like tooling om test coverage - and agreeing with the team on how to go about this - or code review practices and enforcing (or not enforcing) this.<p>When it comes to scaling for millions of users, things like monitoring, alerting, logging, measuring performance in smart ways are things that also need to be done.<p>I happen to head up a web team who is building “scaleable” web apps in this latter regard (we have millions of monthly paying users around the globe whom we need to scale for) and I’ll write up the additional practices we use to “scale” with w small team in a later post on my blog [1] for anyone interested.<p>[1] <a href="http:&#x2F;&#x2F;blog.pragmaticengineer.com" rel="nofollow">http:&#x2F;&#x2F;blog.pragmaticengineer.com</a>