Software developers have been presented with so many tools meant to assist then during the development process. Tools like autocomplete, intelli-sense, linters, and other static analysis solutions. All such tools have one underlying goal, to promote productivity and improve quality. Much research has been conducted on the topic of software quality and its direct benefits both during and after the development cycle. Various methods of measuring and improving quality in software products have been implemented at a grand scale. However, software developers are still left with the choice of implementation details. One such detail is the choice of identifier names in the code written. Few publications have focused on conventions, guides, or best-practices on the topic of identifiers naming choices (not to be confused with coding styles). Much time and energy is misused by developers while choosing an appropriate identifier name, as well as by other developers later on when trying to understand the choice made by their colleagues. By aggregating and compiling a list of readily available identifier names that developers can choose from, will allow them to focus on other keys aspects of development