Here are the rules I live my life by right now. These are subject to change. 1. Don’t make excuses, make progress. 2. It’s only progress if it’s towards something meaningful to you. 3. The best time to make progress was yesterday. The second best time is today. 4. Progress is guaranteed if you learn from your mistakes. That is all.

Okay, let's be honest. Many (and I mean...many) software "engineers" are NOT engineers at all and here's why: 1. They do not use even the most fundamental engineering principals, ever. 2. They do not take time to understand the problem they're trying to solve. 3. They do not take time to understand the current shape of their system. 4....

There’s a pattern/mindset/delusion known as “smart” and “dumb” components. The idea is that smart components understand some domain knowledge (they understand and process the data they’re responsible for), while dumb components do nothing but present data their parent component gives to them (as inputs) and report data back to their pa...

“We’re doing Agile!” What the fuck are you talking about? You’re doing Agile? When did Agile become a proper noun? Also, why are you focused on agility? Why are you having to change direction so often and so quickly? What kind of poor ass decisions are you making? So you know more about your solution than the problem that it’s supposed...

We've all heard it, "design for maintainability" and "once we're in maintenance mode..." What exactly do we mean by this? When I hear this it sounds like, "let's keep our software exactly how it is" and "don't change it." In fact, I think this is exactly what we mean, but for some reason we subconsciously tell ourselves something sligh...