You can hack together a solution. You can overengineer something and never finish. How do you balance the two extremes? What principles help you find the best simple system for now?
Examples can help people learn. The more context your reader has with your example, more effective your example.
Many people think simple and easy are synonyms. They’re not. They’re similar and related, but they’re NOT the same thing.
You’ve probably heard of Type I and Type II errors, but there are other kinds of errors as well. You need to be just as careful of them as well.
If code can have virtues, then tests, which are also code, can have virtues. The question is, are there any special virtues that are unique to tests? Of course there are. Here’s a few virtues which can make your tests better.
Comments are a code smell. You should always look at your code smells. But that doesn’t mean you shouldn’t comment your code.
You’ve probably heard it said that if everyone is responsible, no one is responsible. That can happen, but that doesn’t make it a good thing.
How you describe a situation has a lot of impact on how you approch it. Do you take away or give yourself agency?
Sometimes the fastest way forward is to say No to doing something. The trick is knowing when to say no.
George Boole brought us Boolean logic. There’s tremendous benefit in using it. But sometimes, it can also blind you to a deeper truth.
We deploy code and release features. We usually assume those two things are the same, but are they really? And should they be?
It happens to everyone. What happens next is what’s important. That’s where the blames post-mortem comes in
The Big Lebowski is more than a comedy or whodoneit. It’s a commentary on life. And the inspiration for Dude’s Law.
Where you are influences not just what you see, but how you see it.
It’s important to distinguish the how from the what and the why.
When you say you want quality software, what are you really asking for, and how can you get it?
I got my attribution wrong, and you probably did too, but the point is just as valid.
It Depends is human for the lack of context error code.
It’s good to be DRY, but you can have too much of a good thing
You can rubber duck too much, but please, take a moment to think about the problem before you give up trying.
Balancing forces can make for apparent paradoxes
Shipping sooner by starting less.
Is it really A or B? Could it be A and B? Could it be part of A and part of B? You have a choice