Writing maintainable code is a communication skill
I found out that some fellow engineers do not want to write maintainable code, they instead want to write code that:<p>- follows SOLID principles<p>- follows Clean Code principles<p>- follows Hexagonal architecture principles<p>- ...<p>Sometimes such principles do lead to maintainable code, but, most of the time they don't (at least in my limited working experience of around 10 years). An example: If you duplicate code because at the end it seems to be the proper way to write a piece of functionality that will be easier to maintain in the future (and most importantly, it communicates clearly its intention)... well, that's a no-go for some fellow engineers because, somehow, that violates all or some of the principles they have read in some blog post owned by internet celebrities.