Naming Things
notes
now i need to read a book about cache invalidation!
this might have been just as good as a long essay. on the other hand, essays can be 100 pages...
with that said, i think breaking down concepts that are seemingly intuitive or engrained in our minds is a great exercise. the structure then gives names, guidance and constraints allowing one to better wield the concept at best and at worst, communicate with others about these concepts.
the section about renaming and the difficulty for early teams to get naming right feels both pertinent and likely also the least developed concept in the book. maybe it's just a hard problem.
link
summary
Naming is one of the most difficult and enduring challenges in software engineering, but few of us do it well. This practical and comprehensive book provides a set of principles, rules, and application guidelines for efficiently choosing good names in your code. These skills can be used throughout your career, and they’re useful for every programming language, technical domain, and experience level. The book incorporates real-world examples to illustrate how to choose good names and avoid bad names.