The world of programming is deep and rich, with its own unique culture and terminology. In this article, we introduce several terms, pieces of jargon, and slang that may seem a bit obscure to the general public, but will make programmers say, “Yep, that’s so true.” Each of these terms has its own history and background, and understanding them can give you a deeper appreciation of the programming world.

Contents
  1. Bug
  2. Refactoring
  3. Commit
  4. Pull Request
  5. Dead Code / Zombie Code
  6. God Class
  7. “Licking” the Source Code
  8. Eradori
  9. Conclusion

Bug

A term indicating that there is a problem or defect in a program.

  • Origin:
    In the 1940s, an actual insect (a moth) got inside a computer called the Mark II used by the U.S. Navy and caused a system malfunction. This incident is said to be the origin of the term.

Refactoring

Improving and reorganizing the internal code without changing the program’s external behavior.

  • Origin:
    From the English word “refactor” (to restructure). It is one of the techniques used to keep code clean and maintainable.

Commit

The act of recording modified source code into a version control system.

  • Origin:
    In English, it means “to promise” or “to finalize.” It is used in the sense of permanently saving changes.

Pull Request

A request to merge changes from one branch into another branch.

  • Origin:
    A term used on GitHub, a service based on the Git version control system. The name comes from the idea of “pulling” changes into another branch.

Dead Code / Zombie Code

Code that is no longer executed and has become unnecessary. It was once used, but despite no longer being needed, it still remains in the codebase.

  • Origin:
    It literally means “dead code” in English, expressing the idea that unnecessary code is effectively “dead.”

God Class

A class that has far too many functions and responsibilities. It is difficult to modify or maintain, as a single class ends up handling too much.

  • Origin:
    The name comes from the idea that the class is almost omnipotent, possessing an excessive number of functions.

“Licking” the Source Code

Carefully reading and analyzing someone else’s source code to understand its content and implementation. This expression is often used when examining the internals of external libraries or frameworks, or when closely investigating code during debugging.

  • Origin:
    The exact origin is unclear, but “licking” food implies tasting it carefully and thoroughly. By analogy, this expression came to mean reading source code in great detail. Just as licking symbolizes savoring something completely, “licking” source code metaphorically conveys the intensity and focus involved in deeply understanding it.

Eradori

An abbreviation of “error handling” (literally “error removal”). It refers to the task of finding the cause of an error and fixing it.

  • Origin: A combination of the words “error” and “removal.”

Conclusion

These terms are frequently used in real programming environments. Each one reflects not only technical or historical background, but also the culture and sensibilities of programmers. Hearing these words in everyday contexts can help you appreciate the depth and appeal of programming.

This article is intended for programming beginners and those who are simply interested, explaining the unique language used by programmers. We plan to continue digging deeper into various technical topics and terminology, so if this caught your interest, be sure to check back for more.

　
*Some of the terms included here are not universally recognized, so please use this information at your own discretion.*

Relatable Terms