#abstraction

The more you add, the harder it becomes to understand.

Two design patterns that I’ve found helpful when designing systems to deal with untrusted data.

Compose types and use them to represent complex data in a clean and type safe way.

To make something easy to understand, its parts should be at the same level of abstraction.

Create abstractions to communicate intent to your fellow programmers.

I put stuff with too much uncertainty in a box and don’t think about it until I know more.

Unless you can predict the future, stick to what we know today.

Learn to move from imperative while and for loops to declarative collection functions like map and filter.

Use creation methods when a constructor fails to fully capture the programmer’s intent.

Testability and reusability goes hand in hand. When you test a function, you run the code in another context than it was built for.

How to avoid “temporal dependencies” where things must be done in a certain order.

A selection of functional programming concepts that I feel are helpful to all developers.

How replacing validation functions with types can make your code safer and more expressive.

Most complexity should be in classes with few dependencies, and most dependencies should be in classes with little complexity.

Let the method signature describe “what”, the body “how”, and the caller “why”.