I’ve honestly never worked on software in an environment where the advice in the article wasn’t important to keep in mind. Personal projects, single digit emplo

I’ve honestly never worked on software in an environment where the advice in the article wasn’t important to keep in mind. Personal projects, single digit employee count startups, growth stage, ancient and slow moving Perl monolith shops … they all needed to keep the principles of simplicity, boringness (boring.tech is a great reiteration of this) and continually self-auditing to reduce inherited complexity in mind. Whether or not Google interprets this advice in a sane way or whether they actually follow it are separate issues, but I think the advice is timely and (at least in my experience) important for many people to hear, regardless of where it’s author works.