Test Driven Development

Kent Beck's TDD is good book to start with. Even if you feel like you have got testing figured out, you should try TDD. It has more to do with discipline and getting things done, rather than writing code fast or smart or efficiently. Someone I follow on twitter once called it "thinking at sustainable pace", which is really what TDD is about.

on HN, 2017

The only value provided by TDD when writing new code is that you're forced to think from caller/user perspective, so it makes your API design better, that's it.

on HN, 2023

Listing out the tests you're going to write before you write the code (even mentally) can be considered a continuation of the requirements-gathering process. And thinking about how you're going to test your code before you write it will, in my experience, improve the design.

on HN, 2023

Split the process of development into small steps. One does not always have to design the complete solution beforehand. Periodic improvement/refactoring leads to better solutions than up-front/big design.

on HN, 2022

I encourage junior developers to learn and try to use TDD for a while because it can be useful sometimes and improve the way they write code.

on HN, 2023