Tags
Posted 30 minutes ago · 55,404 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.
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.
Make boring choices.
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.
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 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.
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.
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.
Understanding the problem is half the solution.
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.