A core tenant of writing maintainable code is to write "readable" code. But what does it mean for code to be readable? Can it be measured? Is it even objective? Why does more "readable" code always seem to mean more code? Longer names, more verbose patterns, less creative solutions, and so often "code a junior engineer can understand"? Let's explore this topic, challenge our assumptions, and get to the heart of what it really means to be "readable".