I have a feeling TDD proponents work in very different code bases than I do, the point in this article is spot on that TDD emphasizes nice to have unit tests ov

I have a feeling TDD proponents work in very different code bases than I do, the point in this article is spot on that TDD emphasizes nice to have unit tests over the much trickier but more bug prone integration tests. For frontend dev the surface area of things that can go wrong is much higher than say in programming an api, so just writing the tests for a lot of changes seem much more difficult than writing the code itself, since you won’t know what can go wrong until you build it. A lot of frontend programming is throwing something on the DOM and then trying to understand the weird ways it went wrong, like a scroll bar width is slightly different in every browser, or the line height for a text input behaves unexpectedly if you change a font. I have no idea how you would build these features with TDD. Seems like the more formal your codebase the more useful it is.