The Curious Notes

Say hi

Posted 19 hours ago · 45,376 reads

Readability is not about clever code or terse syntax. It's about making the intent of the code obvious to the next person who reads it—which might be you, six months later, having forgotten everything.

APIs are contracts. Once you publish one, changing it becomes expensive for everyone who depends on it. The cost of breaking changes compounds over time, which is why the boring, conservative choice is usually the right one.

Know your tools deeply.

Code reviews are less about finding bugs and more about ensuring that the team understands why a decision was made. The review is a conversation, not a gate.

Readability is not about clever code or terse syntax. It's about making the intent of the code obvious to the next person who reads it—which might be you, six months later, having forgotten everything.

Terminal emulators are primitive tools compared to modern IDEs, but they force a certain discipline. You can't rely on auto-completion and syntax highlighting to write code for you; you have to understand what you're writing.

Type systems don't prevent bugs—they just catch certain categories of bugs earlier. The real benefit is the documentation they provide about what a function is supposed to do.

Related

More on this topic

The idea that frameworks solve problems is mostly marketing. They shift the nature of the problems, making some things easier and others harder. The trick is choosing the right tools for your constraints.

Optimize for comprehension first.

Legacy code is called legacy for a reason. It works. It's been tested in production. It's often the most reliable code in your system, even if it doesn't follow modern conventions.