Chaos Theory 2.0

When i was a kid, my dad had a CD collection, sorted by the artists names. So - what did my sister and me do, when we wanted to listen to music? Yepp, we teared out twenty CDs from the shelf and spreaded them all over the CD player. When we where supposed to clean up, we jammed them back in without any order. Where we too dumb to stick to a simple A-to-Z sorting? Not at all. We simply didn't care about the order of our father.

Let's jump to the year 2018. When i look from my desk to the right now, there is a CD shelf. Neatly sorted, of course. In conclusion: It is not too difficult to adhere to your own structure. But keeping the order of another person is a skill that needs to be trained!

But what about source code? Well, le'ts have a look at it's conventions. Line Indentation, Parentheses, CamelCase, snake_case... you name it. Sure, PHP and JavaScript has it's own standarts, but still some organisations have special code conventions or prefer specific libraries.

If we just want to expand an existing project with some code, we mix in personal preferences. Or we routinely program according to the conventions of a previous project. It's important to be able to switch consciously. Otherwise we establish two programming paradigms in one codebase and inevitably arises what we originally wanted to avoid: Disorder.

But what about Git requests? Or other tools? Doesn't them solve this issue? Yes, theoretically they do. But what about you save the auditors time and program according to code conventions in the first place? Also, small organizations may have no capacities to check every line of code. So it's never too bad to learn this skill.

Write a comment