Have you ever seen "NaN" appear on a badly coded website? Or been perplexed by a persistent bug, only to find out that it's some quirk with the language? The problem is partly to do with your assumptions and probably an incomplete test suite. I will explain what property-based testing (PBT) is and how it solves these problems.

If you've ever maintained a configuration for an extensible text editor, you'll know it can become a full-blown software project. Making a disaster of it like I did means that adding a new feature fills you with dread. LazyVim tackles that problem with some awesome features, and I'll explain how.

Are you a distro hopper? Then perhaps you can help me see the appeal. To me, the fundamental properties of a system are what make it special, not the superficial changes made every few months. Perhaps I'm wrong? But here's why I think it's a waste of time.

Vibe coding promises to do the heavy lifting while you put your feet up. Except it never works out that way, does it? You waste precious time debugging a codebase you don't understand, going around in circles with a mindless AI. I will explain why vibe coding is a terrible idea.