Open Thread

Writing

Posted 57 minutes ago · 5,607 reads

Most of the code we write is not rocket science. It's ordinary business logic, wrapped in layers of frameworks and abstractions. Sometimes the simplest implementation is the best.

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.

The best abstractions are invisible.

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.

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.

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.

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.

See also

More on this topic

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.

Understanding the problem is half the solution.

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.