I was challenged by @unclebobmartin on why I "lead the boycott of clean code". I've written a blog post to answer his challenge: johannesbrodwall.com/2018/06/24/for…. 1/5
Although there is much sound technical advice in his books, I think it's dyed in an idea of compulsion, honor and shame that I find harmful for the improvement of teams as well as opposed to "people being more awesome". 2/5
I don't want teams to argue over who violates the clean code principle and who didn't do their duty. I want a pleasant conversation about how the team wants code to look.
I don't want to use TDD because of professional compulsion. I want to use TDD when it's fun. 3/5
I don't want to use TDD because of professional compulsion. I want to use TDD when it's fun. 3/5
Why is this relevant now? The outrage over "unhonorably comparing a government to Nazi-ism" mirrors outrage over failure to practice TDD or otherwise living up to @unclebobmartin 's professional standards. Clean code is not the ideal. 4/5
Clean code is not the ideal. It can be a tool to help people be more awesome, but it can also be a source of strife, disagreement and burn-out. When we put rules before people, that will be the result. 5/5
