So much advice in software development presupposes that everyone has the same single goal and at least one inexhaustible resource. In this case, time: - To rea

So much advice in software development presupposes that everyone has the same single goal and at least one inexhaustible resource. In this case, time: - To read and understand all relevant parts of the build pipelines for each performance-critical part of the infrastructure. In a relatively simple web application that could mean at least a web server, a caching framework, a database and a message bus. - To debug any build failures, which could be plentiful and hard to parse until you're very familiar with the build infrastructure for that particular piece of software. - To benchmark the build outputs in comparable ways with realistic configuration and inputs. - To repeat the above whenever any part of the stack changes significantly.