Make code easy to read and extend without breaking it. By now, many of us are aware of the importance of writing tests. However, there is a problem in making th

Make code easy to read and extend without breaking it. By now, many of us are aware of the importance of writing tests. However, there is a problem in making them readable. Here's one Kevlin Henney's lecture [1] that crystallizes it. It took me a long time to find it, so you are welcome. Once you start naming things like this, adding future use cases becomes far less risky and thus you don't need to waste time on them. https://www.youtube.com/watch?v=tWn8RA_DEic https://www.youtube.com/watch?v=tWn8RA_DEic