One of My Main LLM Use Cases as a Developer

ProductivityCodingLarge Language Models

As a developer, one of my primary use cases for using large language models (LLMs) might come as a surprise: brainstorming variable names and other naming conventions. While this might not seem like the most obvious or important application of AI, I realized it has a significant impact on my productivity and efficiency.

Why Naming Matters

Clear and consistent naming is crucial in software development. When variables, functions, git branches, merge requests, database tables, and attributes are named intuitively, the entire codebase becomes easier to read, understand, and maintain. When things are not named properly (are misleading, inconsistent, or vague) it creates unnecessary confusion. This not only makes it harder for me to work efficiently but also affects my future self and teammates who need to navigate the code.

How LLMs Help with Naming Conventions

When I’m stuck trying to name something, I ask an LLM. Here’s how it helps:

  • Generating Ideas – I describe the purpose of a variable or function, and the model suggests multiple naming options. I then review these options and select the one that fits best.
  • Seeking a Second Opinion – When deciding between a few possible names, I ask the LLM to evaluate them and explain which option is better.
  • Validating Ideas – Sometimes, I think a name makes sense, but AI can highlight potential misunderstandings or suggest clearer alternatives.

Using LLMs for naming conventions saves me a lot of time by reducing the mental overhead of naming decisions and allowing me to focus on actual development tasks.

Productivity and Code Readability

When naming is done right, I can stay focused on problem-solving rather than constantly second-guessing my terminology. This leads to:

  • Improved readability, making it easier to revisit old code or onboard new developers.
  • Creating better code, as having things named correctly helps me write better code.
  • Fewer cognitive distractions, as I don’t spend time deciphering unclear names.
  • Better collaboration, since well-named components facilitate smoother communication among team members.

Conclusion

While brainstorming variable names might seem like a small detail, it’s a fundamental aspect of writing clean, maintainable code. By using LLMs to check and refine my naming conventions, I improve my workflow and ensure that my code remains clear and structured.

So next time you find yourself stuck on a name, try asking an LLM. You might be surprised at how much it helps!