Quiet Thread
Log in

Writing

Posted 57 minutes ago · 54,114 reads

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 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.

Simplicity is underrated.

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.

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.

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.

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.

See also

More on this topic

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.

Simplicity is underrated.

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.