The Methodical Notes

About

Posted 1 hours ago · 20,327 reads

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.

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.

The best code is often the code you don't write.

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.

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.

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.

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

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.

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.