$ ls /tags/all posts

A parable about the true cost of naming things incorrectly. When you name something 'Stripe Payment Intent Id,' you create a contract. Break that contract, and you break trust with every system and developer who relies on that name meaning what it says.

When successful people share their secrets, we dismiss them as too simple. We're waiting for hidden complexity while they've already told us the truth: daily practice, boring fundamentals, and years of pattern recognition that looks effortless from the outside.

Applying software engineering principles to company building. Just as code has "smells" that indicate underlying problems, startups have organizational smells that can lead to failure if left unchecked.

Why shipping frequently beats perfect architecture every time, and how the right engineering foundations make aggressive deployment a competitive advantage.

Writing code is just one piece of the puzzle. The true craft of software engineering lies in change logs, ADRs, post-deployment cleanup, test maintenance, and disaster recovery strategies that distinguish senior developers.