Findings Concerning Naming Variable Delay

Classification: Forensic Analysis — Developer Behavior Subject: The Variable Currently Named temp2 Status: Pending Final Name Since Thursday

Background

The function works. This is not under investigation.

The variable holding the intermediate result of a transformation has been named temp2 since Thursday because the developer could not identify a name that was accurate, concise, meaningful to future readers, appropriately abstracted, and short enough that it would not feel like overengineering when encountered six months from now.

temp2 is none of those things. It is still in the codebase.

The Naming Process

The developer generated the following candidates, none of which were accepted:

• result (too vague)
• processedResult (redundant — the context makes processing implicit)
• transformedData (too broad, doesn't specify the transformation)
• normalized (implies a different kind of operation)
• cleanedValue (conversational; may confuse junior developers)
• sanitized (carries security-specific connotations the operation does not warrant)
• outputBuffer (wrong layer of abstraction)
• intermediate (accurate but defeats naming's purpose)

The developer opened a thesaurus. The thesaurus suggested "refined." The variable named refined was worse.

Why the Wrong Name Feels Permanent

A name introduced into a codebase becomes the vocabulary used to discuss the concept. Team members learn it. Code review refers to it. The name propagates horizontally through related variables, comments, and documentation.

A slightly wrong name, introduced into a codebase with regular traffic, can persist for years after its author has left and nobody remains who knows why the thing is called what it is.

The developer is aware of this. The awareness is the cause of the delay.

Current Status

temp2 is shipping tomorrow because the PR has been open for four days and the feature has a dependency.

The developer has added a comment above the variable explaining what it does. The comment will outlast any renaming initiative.

Familiarity outranks correction. The team will learn to say temp2 naturally within three weeks.