Formatting plays a crucial role in creating code that is not only functional but also readable and maintainable. In this article, I will shed light on the code smell associated with neglecting proper line wrapping and explore why it's considered bad practice, too long, isn't it? TL;DR: Extract and wrap your code Problems Hard to read code (especially in small devices) Demeter's Law violation Solutions Wrap the code to at most 75 characters. Break and concatenate long strings. Compilers optimize them. Thinking there's a speed penalty is a mistake. premature optimization Don't use . Abbreviations Context Unwrapped code formatting refers to the absence of line breaks or appropriate indentation. It yields excessively long lines of code that extend beyond the typical width of a code editor or mobile screen. While writing , people read the code on small devices so line wrapping is critical. my last book Sample Code Wrong struct ExtraterrestrialSignal { signal_frequency: f64, signal_strength: f64, signal_duration: f64, }

fn perform_signal_processing_and_analysis(extraterrestrial_signal: &ExtraterrestrialSignal,
) {
    println!(
        "Extraterrestrial Signal processed - Frequency: {} Hz, Strength: {}, Duration: {} seconds", extraterrestrial_signal.signal_frequency,  extraterrestrial_signal.signal_strength, extraterrestrial_signal.signal_duration);

    if extraterrestrial_signal.signal_strength > 0.8 && extraterrestrial_signal.signal_duration > 10.0
    {
        println!("Potential Extraterrestrial Signal of interest!");
    } else {
        println!("Signal does not meet criteria for further investigation.");
    }
} Right struct ExtraterrestrialSignal {
    signal_frequency: f64,
    signal_strength: f64,
    signal_duration: f64,
}

fn perform_signal_processing_and_analysis(
    extraterrestrial_signal: &ExtraterrestrialSignal,
) {
    println!(
        "Extraterrestrial Signal processed" + 
          "- Frequency: {} Hz, Strength: {}, Duration: {} seconds",
        extraterrestrial_signal.signal_frequency,
        extraterrestrial_signal.signal_strength,
        extraterrestrial_signal.signal_duration
    );

    if extraterrestrial_signal.signal_strength > 0.8
        && extraterrestrial_signal.signal_duration > 10.0
    {
        println!("Potential Extraterrestrial" 
            + " Signal of interest!");
    } else {
        println!("Signal does not meet criteria" 
            + " for further investigation.");
    }
} Detection [X] Automatic This is a formatting and syntactic smell Tags Formatting Level [X] Beginner AI Assistants AI assistants sometimes bring short code and not real production code. You can use the assistants to wrap and format your code. Conclusion Ensuring readability is consistently paramount, with various facets warranting consideration. When lines of code are excessively long, developers may find it challenging to understand the structure and flow of the code. Relations https://blog.devgenius.io/code-smell-33-abbreviations-ba5149c93a68 https://blog.devgenius.io/code-smell-48-code-without-standards-60c9e0905627 https://levelup.gitconnected.com/code-smell-164-mixed-indentations-a328947b9a7e https://levelup.gitconnected.com/code-smell-211-tab-over-spaces-66f20522727c More Info Clean Code Cookbook Disclaimer Code Smells are my . opinion Credits Photo by on Olesya Yemets Unsplash The objective of cleaning is not just to clean, but to feel happiness living within that environment. Marie Kondo https://blog.devgenius.io/software-engineering-great-quotes-3af63cea6782?embedable=true This article is part of the CodeSmell Series. https://blog.devgenius.io/how-to-find-the-stinky-parts-of-your-code-fa8df47fc39c?embedable=true

Augmentastic || Augmented Reality

Code Smell 238 - Dealing With Entangled Code

How to Find the Stinky Parts of Your Code [Part XLVII]

Buy My Book

Share your ideas with me!

Read My Stories

Buy Me a Coffee

Book Author

Too Long; Didn't Read

Code Smell 236 - What to Do With Excessively Long Code Lines

Code Smell 236 - What to Do With Excessively Long Code Lines

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

10 Predictions About the Future of Finance

106 Stories To Learn About Clean Code

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

110 Stories To Learn About Refactoring

3 Things Coding And Prose Writing Have In Common According To Cory House

4 Simple Habits For Engineering Teams To Beat Technical Debt

10 Predictions About the Future of Finance

106 Stories To Learn About Clean Code

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

110 Stories To Learn About Refactoring

3 Things Coding And Prose Writing Have In Common According To Cory House

4 Simple Habits For Engineering Teams To Beat Technical Debt

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps