One of the hardest parts about coding is “naming” stuff. When done correctly, anyone can read your code. When done poorly, others may spend significant amounts of time trying to figure out what is going on. The art of clean naming, and yes it is an art, is something that you can practice anytime you code. It is something I make intentional when I code. There are times when naming comes naturally to me. Then there are times when I have no idea when I should name something so I call it x.

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn the art of clean naming in coding and how it can improve code readability and maintainability. Discover best practices for clear and descriptive naming, providing context in variable names, and avoiding abbreviations and magic numbers.

Clean Code: The Art of Clean Naming

who doesn’t love discussions about semantics with co-workers that barely speak english?
<img src="https://media1.giphy.com/media/v1.Y2lkPTc5MGI3NjExN3R3ZG91eG51bm14ZTBjeGx5OTA0ejhicTQ4ejlldmExZG8zdWhmNiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/qiMbLh4WHEZyw/giphy.gif" alt="">
-&gt; ids kredäntschal tabol änd dis is kredäntschal list! FML!

If not properly done, naming can lead to confusion. Sometimes, names need additional context to be fully understood. This is especially true in larger codebases where the same term might be used in different contexts. For example, get could mean anything, but getUserDetails or fetchOrderStatus provides much more context about what the function does.

Hehe abbreviations are a tricky one.
It’s a constant battle between having a spaghetti naming and clarity.
Neither is fun to have, but clarity should win in like 99/100 cases.

I love seeing more people talk about clean coding - it feels like it’s not trendy to talk about it anymore, and yet there are so many benefits.

Few years ago I read clean code by uncle Bob, which by the way is an amazing book for any software developer, and Although it is Java oriented, I was able to implement the same ideas in Ruby, Python, Groovy and Bash script. This is one of the required steps thanks to author Eric Roby for writing this