About
Posted 18 days ago · 7,094 reads
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.
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.
The best code is often the code you don't write.
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.
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.
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.
The most important insight I've had in the last few years is that constraints are a feature, not a bug. When you have unlimited resources, you can solve any problem in a hundred different ways. When you have constraints—limited memory, limited time, limited developers—you're forced to think more clearly.
The best abstractions are invisible.
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.