My recommendations: * avoid hype trains: it is a trap * avoid complexity unless there is business based justification: it is another trap * understand that e

My recommendations: * avoid hype trains: it is a trap * avoid complexity unless there is business based justification: it is another trap * understand that every thing you build needs maintenance * understand that the integrations you build for something you don't build also need maintenance * software has many layers: choose where to be disruptive and where to be conservative * avoid superficial cultural assumptions like "smart good junior people that hug trees will do wonders": you need a couple of pragmatic engineers to impose common sense in the operations * avoid bogus metrics like "I deployed to production 20 times last month" and embrace sound metrics like "we delivered the features on time with few or none bugs found in production" * foster an engineering culture: ensure people understand context, tradeofs and relevant metrics