---
title: "Discussion on \"Code Design Inertia\" | Hashnode"
description: "Discussion on \"Code Design Inertia\". Code Design Inertia:\n\nThe code that will be written in the future will follow the design of the code already written.\n\nInertia is stronger inside a file => the code added will follow the design of the code already written.\nSo going further with this ..."
url: "https://hashnode.com/posts/code-design-inertia/63bfc9ae020abff2a2a044be"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Code Design Inertia](https://codeandgit.hashnode.dev/code-design-inertia?utm_source=hashnode&utm_medium=feed)

Code Design Inertia: The code that will be written in the future will follow the design of the code already written. Inertia is stronger inside a file => the code added will follow the design of the code already written. So going further with this ...

Jan 12, 2023 · 1 min read · codeandgit.hashnode.dev  
Read the article

-   [#code](https://hashnode.com/tag/code)
-   [#programming-tips](https://hashnode.com/tag/programming-tips)
-   [#programming-languages](https://hashnode.com/tag/programming-languages)
-   [#shortpost](https://hashnode.com/tag/shortpost)

## Written by

[Lucian Ghinda](https://hashnode.com/@lucianghinda)

@lucianghinda · Europe

  
[View profile](https://hashnode.com/@lucianghinda)

Senior Product Engineer

Senior Product Engineer, working in Ruby and Rails. Passionate about idea generation, creativity, and programming. I curate the Short Ruby Newsletter.

## Responses 1

Markdown supported · ⌘↵ to post

[Cristian Molina](https://hashnode.com/@megatux)

[Jan 24, 2023](https://hashnode.com/posts/code-design-inertia/63bfc9ae020abff2a2a044be/comment/63cfe74e5e9dc8e3d6908424)

like that thought! These days Rubocop enforce a lot of style and could be very opinionated :)

[Lucian Ghinda](https://hashnode.com/@lucianghinda)

[Jan 24, 2023](https://hashnode.com/posts/code-design-inertia/63bfc9ae020abff2a2a044be/comment/63cfe74e5e9dc8e3d6908424#reply-63cfe8285e9dc8e3d6908444)

Yep, Rubocop is a fantastic tool for enforcing guidelines, and I think using it when working in a team is somehow a reasonable price to pay for writing code that looks similar. Thus when doing a code review or changing code written by a colleague, the mental model is similar; thus, the code is easily understood.

But I am also trying to promote new features. I have a draft article about why to use new language constructs or features :) Hope to publish it in a couple of days