Secrets of a Tech Lead: Programming Principles

Let's talk about one of the core guiding principles I use as a developer and as a Tech Lead when designing solutions and architectures, when programming and when reviewing others code, which I find myself doing more and more as I move forward in my career. These sort of principles are of the family of Ray Dalio's principles but applied to programming, I might write a book about it eventually, who knows. These have have a massive impact in my career as a programmer and have enabled me to get a more holistic approach to designing software that ultimately were one of the main reasons I was able to get a Tech Lead job. With these principles in mind I have a technical compass that helps me navigate all the decision making I need to do all the time; ranging from the high level architectural to the low level naming, function structures, etc. Let's unpack it a little bit, every word counts. Programming can be thought of as a way of expressing ideas in a formal language, in that sense we could even go as far as thinking programming as a weird form of art or even poetry, there are always those pieces of code that touch our hearts, and so long as we have the main goal of software in mind: solving problems, I believe is fine to take this idea of beauty in.