Methodical Margin

Say hi

Posted 9 days ago · 47,365 reads

I've noticed that the best technical decisions come from understanding not just what works, but why it works. The deeper your intuition about a system, the better your architectural choices become.

I've noticed that the best technical decisions come from understanding not just what works, but why it works. The deeper your intuition about a system, the better your architectural choices become.

Make boring choices.

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

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.

Related

More on this topic

I've noticed that the best technical decisions come from understanding not just what works, but why it works. The deeper your intuition about a system, the better your architectural choices become.

Systems thinking matters.

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.