Programmatically Speaking

Why Naming Things Matters More Than You Might Think

One of the most useful technical habits I’ve picked up recently has nothing to do with writing code. It’s naming things. At first glance, file and folder names seem trivial. After all, what’s the difference between: Final Project and project-final-v1? Quite a bit, as it turns out.

The deeper I’ve ventured into systems thinking, development workflows, and Linux-oriented tooling, the more I’ve come to appreciate that naming conventions are really about reducing friction between humans and computers. I like to think of this as improving your HCS-IQ: Human-to-Computer Systems Intelligence. The idea is simple. The easier your information is for both you and your tools to understand, the easier it becomes to search, automate, organize, and scale.

A few principles have stood out to me:
• Use lowercase whenever possible
• Avoid spaces in filenames and folders
• Use hyphens to separate words
• Organize information by purpose and context

Choose names that describe function rather than temporary intent.

For example:
Instead of “Assets” try “project-assets.” Instead of “Final Final Version” try “brand-guide-v3.” Or, instead of: “Random Notes” try “linux-study-notes.” These small changes may seem insignificant at first, but they compound quickly. Command-line tools work better. Search becomes easier. Automation becomes cleaner. Future-you becomes less confused.

The easier your information is for both you and your tools to understand, the easier it becomes to search, automate, organize, and scale.

What surprised me most is that this isn’t really about Linux, programming, or development. It’s about communication. A good naming convention is simply a shared language between you and your tools. And like any good language, clarity pays dividends.

I’m currently experimenting with these practices in my own workflows and projects. So far, the results have been encouraging. Less hunting. Less friction. More connecting. More doing.

Sometimes the smallest systems improvements create the biggest leverage.
—BiBiBi ;B