The 60 Tech-Lead & CTO principles

The code is the source of truth Think of the information system as an ocean Constrain first, relax later Generated technical documentation or nothing Document the rationale Favor a library-first approach No point creating conventions without automation Naming should be boring Put the most constraints upfront Steer the future structurally Prefer declarative over imperative Prefer explicit over implicit Acknowledge inherited debt and tame chosen debt Stay consistent even in error Separate concerns Single source of truth Limit everything in space and time Every constant must be configurable Use human map/reduce sparingly

Get developers to production as fast as possible Bottlenecks are the enemy Teams are on call for each other’s production Start from the assumption that it will break sooner or later No monitoring without alerting Monitor from the user’s point of view

The company is only one of its product’s customers Graphical user interfaces as finite-state machines Keep the balance between product and technical vision Don’t forget to make money Give the power back to the business If it needs training: it’s badly designed If you have a UAT environment, you’ve failed your product Your brand is your design system