Towards the end of my tenure in a team, a new boss instituted mandatory viewing sessions of Martin's training videos; I grew somewhat averse of them. While the

Towards the end of my tenure in a team, a new boss instituted mandatory viewing sessions of Martin's training videos; I grew somewhat averse of them. While the heart of Martin's teachings are about expressivity and semantics, the praxis is much more about recipes than about what matters to me as a professional, which is: 1. Well-definedness of the computation being done (in a mathematical sense of the word), 2. Engineering, that is establishing of a connection between human narratives about what the SW should do with the program's structure. Overall, it seemed to me that Martin is first and foremost trying to sell to sell a certain paradigm of competency to corporate cookie-cutter-culture organizations. My issues with this paradigm of competency are that: 1. Doing it properly requires a massive investment, which does not make business sense. 2. As is often the case, this paradigm makes it easy to feign competence without actually being competent, which is damaging to organizational trust.