4 ms·
The best coding styles are the ones that allow to be translated back and forth to another style. It doesn't matter which style you prefer. As long as a compute
by aequitas 8y ago
The best coding styles are the ones that allow to be translated back and forth to another style.
It doesn't matter which style you prefer. As long as a computer can pick it up and translate it into the project standard style and back to yours again. You can simply setup git filters and live in you own style world.
- swalladge 8y agoUsing git filters is a great idea! I've heard of this for translating between unix and dos line endings in git, but hadn't thought about using it for entire styles. There are heaps of automatic code formatting tools becoming more popular these days too.
- deckard1 8y agoCode is meant to be read first and foremost by humans. As such, code should be written for clarity and presentation. To communicate intent. Automated tools destroy this human/code connection. They reduce your coworkers to simple cogs in a machine, rather than authors and communicators. I'm not a fan of this cold, brave new world.
- aequitas 8y agoHow code is styled doesn't distract from the main purpose to communicate intent. Most often humans are the ones mindlessly layering on the meaningless formatting/style on top of syntax and its then becomes the pivotal point of code reviews, burying the essence of the code. I applaud companies like Google and Hashicorp for forcing formatting as compilation errors. As it lets you get on with the real tasks ahead.