Hacker News Reader

> writing code that can be deleted is an important skill

Are you saying "I can easily delete this code from the project" is a metric for modularity? That's really interesting, is it your own thought?

View on HN

I saw it before. Deletion Driven Development is one of the many names. For me a good rule of thumb is: removal of a feature should result in a diff that deletes a bunch of files (classes in case of oop) completely, and only single lines in other files: the call sites to that feature.

Write code that is easy to delete, not easy to extend: https://news.ycombinator.com/item?id=11093733

Reply on news.ycombinator.com