What is so wrong with TDD?

This question was posted recently in Quora. I read other’s answers first and felt an itch to share my thoughts on it. Thereafter, I published it as a post in Hackernoon which caught a zillion eye-balls and heck a lot of readers time. 

This post is a re-production of that after a good couple of years now, for I think this is still relevant.

I hate TDD (aka Test Driven Development) and think there are a lot of things wrong with it. Only some of them off my mind are below.

copyright: codonomics

Top 10 FacePalm Things I Witnessed In The Enterprise World

1. When a developer proposes with beaming pride to trim error stack-trace to a few lines, to reduce logging footprint. 😭😭😭😭😭
2. When a Tech Lead does not show technical inclination to learn things. 😭
3. When a Tech Lead takes boasts of attempting to fix memory leak in enterprise java application by uploading code/memory-dump to third-party site thus breaching corporate security policy. 😭
4. When a Manager/Management is callous about blatant breach in security practices and does not take mitigation/containment plans. 😭😭😭
5. When a Program Manager has no clue about the Product Roadmap and doesn't care about the big-picture. 😭
6. When a Program Manager has no clue about the Program Roadmap and doesn't care about the big-picture. 😭
7. When a Product/Program Manager attempts to steal the credits of the technical work done by developer(s). 😭
8. When Project teams crave for individual credits over working together with other stakeholders to achieve the  big organisational vision. 😭😭
9. When the Management is focused in vendetta politics instead of working towards the program milestones. 😭😭😭😭😭
10. When developers partake in management politics of cannibalism for quick wins instead of long term team harmony and learning together. 😭😭

Got even nastier things to share? Don't hesitate to dump your thoughts over comments and maybe feel a little lighter. Cheers!