I Created a Nightmare of Names

Jeez, I am a seasoned IT engineer, aren’t I?

Let me explain from the beginning.

For an assignment at UoPeople, I created an assembly program. Since the assignment name is Assignment Activity, I named the program file aa.asm, the assignment name’s abbreviation, without thinking carefully. I thought the name was terrible inwardly, but I somehow submitted this program. How brave I was!

Later, for another assignment, I read a designated textbook. It explains in detail the procedures for creating a simple assembly file, compiling it, and executing it. It also says that an untrained programmer tends to create a nightmare of naming. Wow. It is me! Apparently, I am an untrained programmer!

Indeed, the file name aa.asm is unbelievably horrible. No one can suppose that it is an abbreviation of the assignment name. I certainly will never name production programs that. If someone in my team names a source file that I undoubtedly point out during a review. Why did I submit the assignment in such a dreadful name, despite the fact that I understood that it was a bad practice in the back of my mind? Maybe I felt bothered about renaming and modifying the part of the source code that imports the external file, which is also named function-for-aa.asm. Wow! For such a trivial thing?

As shown in this case, once I determined something, modifying it later feels somehow disturbing. It is important to carefully consider the specifications before writing actual code. Honestly, this is a common practice in professional development settings, too. Well, programmers often cannot wait to write code before the requirements are fixed. That is, I am a seasoned IT engineer after all!