---
title: "Discussion on \"Naming: if you have to open the body, the name isn't done\" | Hashnode"
description: "Discussion on \"Naming: if you have to open the body, the name isn't done\". Everyone I've worked with agrees that naming matters. Almost nobody spends any time on it. The name gets picked while the code is half written and then it sticks, because renaming feels like fuss once"
url: "https://hashnode.com/posts/naming-if-you-have-to-open-the-body-the-name-isn-t-done/6a97fee7b71233486a849403"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Naming: if you have to open the body, the name isn't done](https://prickles.hashnode.dev/naming-if-you-have-to-open-the-body-the-name-isn-t-done?utm_source=hashnode&utm_medium=feed)

Everyone I've worked with agrees that naming matters. Almost nobody spends any time on it. The name gets picked while the code is half written and then it sticks, because renaming feels like fuss once

Sep 2 · 3 min read · prickles.hashnode.dev  
Updated Sep 4  
Read the article

-   [#clean-code](https://hashnode.com/tag/clean-code)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[Adam Lewis](https://hashnode.com/@nark3d)

@nark3d · Bedford, UK

  
[View profile](https://hashnode.com/@nark3d)

Product Engineer/Architect navigating the AI revolution

I'm a working software engineer. Most of what I write comes from the same place: code is easy to generate now and just as easy to make unmaintainable, and the old engineering habits matter more for it, not less. prickles.org is where I collect those habits as short, specific tenets — guard clauses, screaming architecture, verifiable specs, and the rest. If something here is useful, that's where the full set lives.

## Responses 1

Markdown supported · ⌘↵ to post

[Rodrigo Juarez](https://hashnode.com/@rodrigojuarez)

[Sep 2](https://hashnode.com/posts/naming-if-you-have-to-open-the-body-the-name-isn-t-done/6a97fee7b71233486a849403/comment/6a986d5201972ae1b7e00489)

I will tirelessly rename anything that becomes outdated as my understanding of the domain evolves. I mean, the agent will do it. That's why I have hundreds of tests.

I also find that renaming is a great way to expose places where the model is wrong. If something is difficult to name properly, it often points to a bad abstraction, misplaced responsibilities, poor functionality grouping, or something else that needs rethinking.