Personally, I find that a couple weeks of TDD each quarter is enough of a boost to your design thinking to make a substantial improvement in how you design things. I don’t know how long a new engineer needs to do TDD to “get it” but I know for sure that you don’t need to do it for 10 years consistently.
If you’re really struggling to test a piece of code, sometimes it’s useful to stash all the changes and start with the tests. That’s a very good sign you’ve lost your way, and you can reflect later on whether it’s a pattern or just a bad day.
Pain is information. If you make use of the information then it redeems itself. If you don’t then it’s just needless suffering.
Comments
Personally, I find that a couple weeks of TDD each quarter is enough of a boost to your design thinking to make a substantial improvement in how you design things. I don’t know how long a new engineer needs to do TDD to “get it” but I know for sure that you don’t need to do it for 10 years consistently.
If you’re really struggling to test a piece of code, sometimes it’s useful to stash all the changes and start with the tests. That’s a very good sign you’ve lost your way, and you can reflect later on whether it’s a pattern or just a bad day.
Pain is information. If you make use of the information then it redeems itself. If you don’t then it’s just needless suffering.