---
title: "Comment by Rodrigo Juarez on \"Naming: if you have to open the body, the name isn't done\" | Hashnode"
description: "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 t"
url: "https://hashnode.com/posts/naming-if-you-have-to-open-the-body-the-name-isn-t-done/6a97fee7b71233486a849403/comment/6a986d5201972ae1b7e00489"
---

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

Comment [Naming: if you have to open the body, the name isn't done](https://hashnode.com/posts/naming-if-you-have-to-open-the-body-the-name-isn-t-done/6a97fee7b71233486a849403)

[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.