“The moral of the story is simple: Test code is just as important as production code. It is not a second-class citizen. It requires thought, design, and care. It must be kept as clean as production code.”
― Clean Code: A Handbook of Agile Software Craftsmanship
― Clean Code: A Handbook of Agile Software Craftsmanship
“So, another way to know that a function is doing more than “one thing” is if you can extract another function from it with a name that is not merely a restatement of its implementation”
― Clean Code: A Handbook of Agile Software Craftsmanship
― Clean Code: A Handbook of Agile Software Craftsmanship
“We do not want to expose the details of our data. Rather we want to express our data in abstract terms. This is not merely accomplished by using interfaces and/or getters and setters. Serious thought needs to be put into the best way to represent the data that an object contains. The worst option is to blithely add getters and setters.”
― Clean Code: A Handbook of Agile Software Craftsmanship
― Clean Code: A Handbook of Agile Software Craftsmanship
“Creating consistency is like making small promises throughout the interface (when you see a pink button it is always an action; the “Cancel” button always comes before “Submit”). When people can be confident of what will happen, they can rely on the product. Consistency helps to build trust.”
― Design Systems
― Design Systems
“Code at the boundaries needs clear separation and tests that define expectations. We should avoid letting too much of our code know about the third-party particulars. It’s better to depend on something you control than on something you don’t control, lest it end up controlling you.”
― Clean Code: A Handbook of Agile Software Craftsmanship
― Clean Code: A Handbook of Agile Software Craftsmanship
Matt’s 2024 Year in Books
Take a look at Matt’s Year in Books, including some fun facts about their reading.
Favorite Genres
Polls voted on by Matt
Lists liked by Matt























