Things I don't like about TDD:
- I think the test name separation by unit test/integration test/micro test/behaviour test doesn't work, but I'm not sure what's the best way to separate them yet
- like fast/slow/io/non-io? business/technical?structure vs behaviour?
- what can tests/refactoring help to catch undefined/NPE at compile time more and not at runtime? (it's harder to refactor with dynamic language)
- how do we get fast feedback on things like build/infrastructure and security? Where tests are hard to write, and maybe technology is not there yet?
- how do I write tests that last longer? Like, communicate business intent and not internal details and technical details?
- TDD requires changing mindset, and it's hard to get adopt where psychological safety and maybe the technology doesn't support it.
- in the hostile codebase (with dynamic language), where there's no test and no psychology safety, how can I decouple the dependencies first to put in tests without breaking production code?
- How can TDD help me better organize/maintain the architecture where the layers/modules are separated clearly?
- how can TDD help me discover reinforcing loops (postive/negative) feedback loop faster? (like what's the core domain?)
Things I do like about TDD:
- easier to make change
- a safety net to protect me when my assumption is wrong or I make mistake, which I will
- better/easier to communicate the intent and collaborate with non-technical team members
