Phases of Naming
Phases of Naming

Photo by Florian Olivo on Unsplash

As a young programmer coming out of College with “no experience but abundance of enthusiasm” I was always focused on getting things done. The idea of making sure that my code was clean and readable for anyone else other than me never crossed my mind.

Clean code, a book by Robert C. Martin (Uncle Bob), was something that got started me on the journey to look back at my practices and try to better them one way or another. But one principle in particular that I’m still struggling to get better at is the Convention of Naming.

This article is not intended to provide instructions/solutions as to how one should go about Naming Conventions in code, but rather my own struggles with it. I’m not even sure whether everyone goes through this struggle when it comes to programming or was it just me. Though I would like to believe that everyone out there at some point in the career faced the same dilemma which is

What are the proper etiquettes for naming variables/functions?

Now if you go about Uncle Bob’s book, you’ll find instructions like

“Focus on whether the code reads like paragraphs and sentences, or at least tables and data structure.”

(I would suggest everyone to go read the book at least once)

What follows below is a progression of approach towards naming conventions in my career as a programmer.
['Sarib Mahmood']
['Life Lessons', 'Clean Code', 'Software Engineering', 'Technology', 'Developer']