Another good one is YAGNI. You Aren't Going to Need It. Basically, don't optimize for standards you'll never actually need. If you're writing say, a webapp tha

Another good one is YAGNI. You Aren't Going to Need It. Basically, don't optimize for standards you'll never actually need. If you're writing say, a webapp that at most is expected to serve maybe 100 to 200 users from a single deployment, you don't need a full blown serverless stack with half a dozen microservices to handle all your requests, just get a decent VPS, configure both nginx and the server workers properly and consider caching the database heavy requests using say, memcached. Throw in a round-robin of multiple deployments "as needed" and unless you're hitting "big social media company" levels of traffic and you can scale up to pretty insane degrees.