Make your code look the same everywhere for everybody Make your code look the same everywhere for everybody TL;DR: When machines generate large amounts of code, you need to apply one consistent style to all files. TL;DR: When machines generate large amounts of code, you need to apply one consistent style to all files. Problems Addressed 😔 Inconsistent tabs
Mixed spaces
Uneven braces
Disordered methods
Inconsistent indentation
Mixed formatting styles
Random spacing patterns
Scattered method ordering
Irregular brace placement
etc, etc. Inconsistent tabs Mixed spaces spaces Uneven braces Disordered methods Inconsistent indentation indentation Mixed formatting styles formatting styles Random spacing patterns Scattered method ordering Irregular brace placement etc, etc. Related Code Smells 💨 https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-x-i7r34uj https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-x-i7r34uj https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxiii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxiii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xliii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xliii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xviii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xviii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxv https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxv Steps 👣 Choose a consistent indentation standard (tabs or spaces)
Apply uniform brace placement rules throughout files
Standardize spacing around operators and keywords
Organize methods with public declarations before private ones
Configure automated formatting tools to maintain standards
Create tests to enforce your rules
Apply them as a hook for git commits
Teach your AIs to memorize these rules when generating code
etc, etc. Choose a consistent indentation standard (tabs or spaces) Apply uniform brace placement rules throughout files Standardize spacing around operators and keywords Organize methods with public declarations before private ones Configure automated formatting tools to maintain standards Create tests to enforce your rules Apply them as a hook for git commits hook for git commits Teach your AIs to memorize these rules when generating code memorize these rules etc, etc. Sample Code 💻 Before  🚨 class User{
private name;
    public email;
  
constructor(name,email) {
this.name=name;
        this.email = email;
}

    private validateEmail() {
return this.email.includes('@');
    }

public getName(){
        return this.name;
}

  public setName(newName)
{
    this.name=newName;
  }
} class User{
private name;
    public email;
  
constructor(name,email) {
this.name=name;
        this.email = email;
}

    private validateEmail() {
return this.email.includes('@');
    }

public getName(){
        return this.name;
}

  public setName(newName)
{
    this.name=newName;
  }
} After 👉 class User {
  public email;
  private name;
  
  // Step 1: Choose consistent indentation (2 spaces)
  // Step 4: Public methods before private ones
  constructor(name, email) {
    this.name = name;
    this.email = email;
  }
  
  public getName() {
    return this.name;
  }
  
  // Step 3: Standardize spacing around operators
  public setName(newName) {
    this.name = newName;
  }
  
  // Step 2: Apply uniform brace placement
  private validateEmail() {
    return this.email.includes('@');
  }
} class User {
  public email;
  private name;
  
  // Step 1: Choose consistent indentation (2 spaces)
  // Step 4: Public methods before private ones
  constructor(name, email) {
    this.name = name;
    this.email = email;
  }
  
  public getName() {
    return this.name;
  }
  
  // Step 3: Standardize spacing around operators
  public setName(newName) {
    this.name = newName;
  }
  
  // Step 2: Apply uniform brace placement
  private validateEmail() {
    return this.email.includes('@');
  }
} Type 📝 [x]Automatic [x]Automatic [x] Safety 🛡️ This refactoring is safe, as it only changes visual formatting without altering the code's behavior. Modern IDEs and formatters can apply these changes automatically without risk of introducing bugs. Why is the Code Better? ✨ You improve readability and make your code easier to navigate. You remove the mental overhead of switching styles across files. Your code reviews will focus on meaningful semantic changes. Consistent formatting reduces cognitive load when reading code, makes code reviews more focused on logic rather than style, and enables better collaboration between team members. You also establish a foundation for maintainable code that new developers can understand quickly. How Does it Improve the Bijection? 🗺️ You create clearer visual representations that mirror the logical structure of your real-world  domain. real-world When formatting reflects the hierarchical relationships and importance levels in your business logic, you maintain better alignment between the problem space and solution space. Limitations ⚠️ You need team-wide agreement on formatting standards to be effective. Different team members might have strong preferences for specific styles. Large codebases require significant time investment and coordination to apply uniform styling across all files. Refactor with AI 🤖 Suggested Prompt: 1. Choose a consistent indentation standard 2. Apply uniform brace placement rules throughout files 3. Standardize spacing around operators and keywords 4. Organize methods with public declarations before private ones 5. Configure automated formatting tools to maintain standards 6. Create tests to enforce your rules Suggested Prompt: 1. Choose a consistent indentation standard 2. Apply uniform brace placement rules throughout files 3. Standardize spacing around operators and keywords 4. Organize methods with public declarations before private ones 5. Configure automated formatting tools to maintain standards 6. Create tests to enforce your rules Without Proper Instructions

With Specific Instructions



ChatGPT

ChatGPT



Claude

Claude



Perplexity

Perplexity



Copilot

Copilot



You

You



Gemini

Gemini



DeepSeek

DeepSeek



Meta AI

Meta AI



Grok

Grok



Qwen

Qwen Without Proper Instructions

With Specific Instructions



ChatGPT

ChatGPT



Claude

Claude



Perplexity

Perplexity



Copilot

Copilot



You

You



Gemini

Gemini



DeepSeek

DeepSeek



Meta AI

Meta AI



Grok

Grok



Qwen

Qwen Without Proper Instructions

With Specific Instructions Without Proper Instructions Without Proper Instructions With Specific Instructions With Specific Instructions ChatGPT

ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT Claude

Claude Claude Claude Claude Claude Claude Claude Perplexity

Perplexity Perplexity Perplexity Perplexity Perplexity Perplexity Perplexity Copilot

Copilot Copilot Copilot Copilot Copilot Copilot Copilot You

You You You You You You You Gemini

Gemini Gemini Gemini Gemini Gemini Gemini Gemini DeepSeek

DeepSeek DeepSeek DeepSeek DeepSeek DeepSeek DeepSeek DeepSeek Meta AI

Meta AI Meta AI Meta AI Meta AI Meta AI Meta AI Meta AI Grok

Grok Grok Grok Grok Grok Grok Grok Qwen

Qwen Qwen Qwen Qwen Qwen Qwen Qwen Tags 🏷️ Standards Standards Related Refactorings 🔄 https://hackernoon.com/improving-the-code-one-line-at-a-time?embedable=true https://hackernoon.com/improving-the-code-one-line-at-a-time?embedable=true Level 🔋 [x]Beginner [x]Beginner [x] See also 📚 https://git-scm.com/book/ms/v2/Customizing-Git-Git-Hooks?embedable=true https://git-scm.com/book/ms/v2/Customizing-Git-Git-Hooks?embedable=true https://windsurf.com/editor/directory?embedable=true https://windsurf.com/editor/directory?embedable=true Credits 🙏 Image by Michal Jarmoluk on Pixabay Michal Jarmoluk Pixabay 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?embedable=true

The code in this story is for educational purposes. The readers are solely responsible for whatever they build with it.

Make

Code Smell 04 - Stop Abusing Strings—Use Real Objects Instead

Code Smell 03: Functions Are Too Long - Here's How to Fix That

Buy My Book

Share your ideas with me!

Read My Stories

Buy Me a Coffee

Too Long; Didn't Read

Make resilience your competitive advantage

Refactoring 032 - Apply Consistent Style Rules

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Code Smell 309 - Query Parameter API Versioning

The Conductor in Your Pocket: How PowerInfer-2 Orchestrates Smartphone Hardware for LLM Inference

A Practical Guide to Scalable Job Scheduling for Cloud and Big Data

Running Out of Stock? How Mathematics Guarantees Welfare in Posted‑Price Sales

106 Stories To Learn About Clean Code

Code Smell 309 - Query Parameter API Versioning

The Conductor in Your Pocket: How PowerInfer-2 Orchestrates Smartphone Hardware for LLM Inference

A Practical Guide to Scalable Job Scheduling for Cloud and Big Data

Running Out of Stock? How Mathematics Guarantees Welfare in Posted‑Price Sales

106 Stories To Learn About Clean Code

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps