If I see a Variable that doesn't change. I call that variable a constant

TL;DR: Be explicit on what mutates and what doesn't.

Problems Addressed πŸ˜”

https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxii?embedable=true

https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxvi?embedable=true

https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxiv?embedable=true

Context πŸ’¬

Variables that never change their value are not really variables.

They’re constants pretending to be mutable state.

When we declare something as a variable, we tell the reader (and the compiler) to expect change.

If that change never happens, we’re sending misleading signals about what the code actually does.

Converting these to constants shrinks the state space a developer must track.

A constant signals that a value won’t change, preventing accidental reassignments and letting the compiler optimize better.

It’s honest: if something shouldn’t mutate, don’t let it.

Steps πŸ‘£

  1. Find the scope of the variable
  2. Define a constant with the same scope
  3. Replace the variable

Sample Code πŸ’»

Before 🚨

let lightSpeed = 300000;
var gravity = 9.8;

// 1. Find the scope of the variable
// 2. Define a constant with the same scope
// 3. Replace the variable

After πŸ‘‰

const lightSpeed = 300000;
const gravity = 9.8;

// 1. Find the scope of the variable
// 2. Define a constant with the same scope
// 3. Replace the variable 

// If the object is compound, 
// we might need Object.freeze(gravity);

Type πŸ“

[X] Automatic

IDEs can check if a variable is written but never updated.

Safety πŸ›‘οΈ

This is a safe refactoring.

Why is the Code Better? ✨

Code is more compact and declares intent clearly.

Take it further with language-specific operators like constfinal, or let.

The scope becomes obvious at a glance.

How Does it Improve the Bijection? πŸ—ΊοΈ

This refactoring improves bijection by making it clear what mutates and what doesn't.

In the real world, most values don't change. They're constants.

Declaring them as variables creates coupling between what we're thinking and how we wrote it.

Constants remove that gap and align the code with the actual domain.

Tags 🏷️

Level πŸ”‹

[X] Beginner

https://hackernoon.com/improving-the-code-one-line-at-a-time?embedable=true

Refactor with AI πŸ€–

Suggested Prompt: 1. Find the scope of the variable.2. Define a constant with the same scope.3. Replace the variable

Without Proper Instructions πŸ“΅

With Specific Instructions πŸ‘©β€πŸ«

See also πŸ“š

https://hackernoon.com/is-it-crystal-clear-for-everybody-that-a-date-should-not-mutate-wuoy3z03?embedable=true


This article is part of the Refactoring Series

https://maximilianocontieri.com/how-to-improve-your-code-with-easy-refactorings?embedable=true

https://maximilianocontieri.com/how-to-improve-your-code-with-easy-refactorings