tl;dr:“A common pitfall that many companies face is the temptation to staff a product team quickly and from scratch with a large number of mostly external developers.” Phase (1): Lay the Foundations with a minimal team i.e. 1-3 entrepreneurial engineers and domain expert (2) Expand with precision: 1-2 engineers who match the culture and work ethic. (3) Scale through specialized feature teams.
tl;dr:Principles you should always follow: (1) Async or defer load, consider the critical path. (2) Tree-shake, consciously bundle and eliminate dead code. (3) Define and respect a performance budget. Principles you should follow when possible: (4) Stick to the web platform APIs and web standards. (5) Use new generation frontend frameworks. Patrick discusses each in this post.
tl;dr:“Are you a software architect and often find it difficult to make architecture decisions in your team? This article shows you how to use architecture principles to make effective decisions in your team.”
tl;dr:Technical article where Patrick creates a guide on how to find the right web frontend architecture that fits your specific quality goals, and discusses architecture styles with their different rendering techniques.
tl;dr:"This guide shows you how to write, structure, visualize and manage software architecture documentation in a lean way using appropriate documentation tools."