CoDe SmElL 159 - mIxEd_cASe

Photo by Wolfgang Hasselmann on Unsplash

CoDe SmElL 159 - mIxEd_cASe

Serious development is done by many different people. We have to start agreeing.

Maxi Contieri
·Aug 19, 2022·

2 min read

Subscribe to my newsletter and never miss my upcoming articles

Play this article

Table of contents

  • Problems
  • Solutions
  • Context
  • Sample Code
  • Detection
  • Exceptions
  • Tags
  • Conclusion
  • Relations
  • More Info
  • Disclaimer
  • Credits

TL;DR: Don't mix different case conversions


  • Readability

  • Maintainability


  1. Choose a case standard

  2. Hold on to it


When different people make software together they might have personal or cultural differences.

Some prefer camelCase🐫, others snake_case🐍, MACRO_CASE🗣️, and many others.

Code should be straightforward and readable.

Sample Code


    "id": 2,
    "userId": 666, 
    "accountNumber": "12345-12345-12345",
    "UPDATED_AT": "2022-01-07T02:23:41.305Z",
    "created_at": "2019-01-07T02:23:41.305Z",
    "deleted at": "2022-01-07T02:23:41.305Z"


    "id": 2,
    "userId": 666, 
    "accountNumber": "12345-12345-12345",
    "updatedAt": "2022-01-07T02:23:41.305Z",
    "createdAt": "2019-01-07T02:23:41.305Z",
    "deletedAt": "2022-01-07T02:23:41.305Z"
  // This doesn't mean THIS standard is the right one


[X] Automatic

We can tell our linters about our company's broad naming standards and enforce them.

Whenever new people arrive at the organization, an automated test should politely ask him/her/.. to change the code.


Whenever we need to interact with out of our scope code, we should use the client's standards, not ours.


  • Naming


Dealing with standards is easy.

We need to enforce them.


More Info

All naming conventions


Code Smells are just my opinion.


Photo by Wolfgang Hasselmann on Unsplash

If you have too many special cases, you are doing it wrong.

Craig Zerouni

This article is part of the CodeSmell Series.

Share this


Technical Opinions are my own. I don't have the revealed truth.

Software Design is a creative activity. These are hints and not rigid rules.

I write on BackEnd Business Systems and OOP Design. My advice/experience might not suit other systems.

You can write me at info(at)