#simplicity

Complexity will increase until overwhelming, but striving for simplicity can slow it down.

If you can make an unknown situation look like one you already know how to handle, you can apply a well-known solution.

The secret of good programming is to strip every statement to its cleanest components.

An example of how collection pipelines can help solving an Advent of Code problem.

Beginners use basic tools due to lack of skill, while advanced developers chose them because they know they’re often enough.

Treat every support issue as a bug. Then fix that bug!

Follow the original task for as long as it takes to complete it. Keep a list of everything else.

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

Remove everything that has no relevance to the design.

The best design does what it needs to, and no more.

I believe smaller solutions lead to faster completion and higher quality.

If you don’t know what message to write, it was too long since you last committed.

Has the backlog become longer than you can finish within a reasonable time frame?

It’s easy to think that large results require large changes. That is not necessarily true.

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

How come people never worry about whether technology scales down to a low number?

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

A question which can help you both prioritize more effectively and design better systems.

When you make an exception from a rule, you make the whole system harder to learn.

In technology choices, sometimes “boring” can be better than “interesting”.