If you don't know what your code should be doing, you have no business writing any code anyway!

4 surprising ways that small batches affect us psychologically

5 ways smaller releases, pull requests, user stories, and commits can improve your code

When copying a test, make your changes from the bottom up, renaming the copied function as the last step.

The unit of test in TDD is a behavior. That may correspond to a "unit." It often does not.

TDD has a built-in "check bit" to help ensure that your tests are valid.

My lazy brain sometimes tries to take TDD shortcuts. This always bites me in the rear end.

How do you avoid days-long pull requests? How do you make your changes smaller?

Who is responsible for unit, integration, and acceptance testing? Developers.

Test coverage for its own sake is dangerous. It leads to foolish technical choices.

If code offers business value, it's worth ensuring correctness with tests. If it's not worth doing correctly, just delete it.