Discover a few performance-enhancing guiding concepts and discover how to apply them to the software development environment.
Throughout my more than ten years of experience working on different client projects and products, I’ve had numerous chances to focus on various facets of web application performance. Naturally, this isn’t how things operate; people frequently want me and my team to “implement performance.” Nothing can be improved by a list of 10 specific actions that everyone must take every time. As an alternative, I’ve discovered that it works incredibly well to have a performance-oriented attitude and adhere to a number of guiding principles and abstract ideas. These will then convert into various specific behaviours within a given setting.
Software and system performance have always piqued my curiosity, so I started sharing random things I had learned from time to time. I spoke on this subject at WordCamp Netherlands a few weeks ago. (If you’re interested, the slides are available online.)
In his capacity as a Principal Engineer, Thorsten offers technical direction and mentorship as well as assistance in the adoption of best practices, procedures, and techniques that produce an advanced, effective, and scalable engineering discipline.
Thorsten Frommen
What Is Performance Anyway?
Prior to delving into best practices and associated factors, it is imperative to grasp the definition of “performance.” When people hear the word “performance” in relation to web development, they frequently think of Google Lighthouse, PageSpeed Insights, front-end performance, or Core Web Vitals. That in and of itself is not incorrect, but this is either too general or too narrowly targeted.
Prior to delving into best practices and associated factors, it is imperative to grasp the definition of “performance.” When people hear the word “performance” in relation to web development, they frequently think of Google Lighthouse, PageSpeed Insights, front-end performance, or Core Web Vitals. That in and of itself is not incorrect, but this is either too general or too narrowly targeted.
Conclusion
It takes a solid grasp of every component to write a project’s initial code and to monitor and enhance its performance. The programming language, the architecture, the implementation specifics, the infrastructure, the third-party libraries, the programming and algorithmic principles used, or the environment-specific APIs to be utilised. There is no way around being aware of your surroundings and tools.
