Writing
Posted 42 minutes ago · 51,126 reads
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.
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.
Make boring choices.
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.
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.