31 ms·
Great tool, thanks for this. I've been massively annoyed with the obsession of making the code look exactly the same in every of its parts. Ten years ago, I co
by oelmekki 9y ago
Great tool, thanks for this.
I've been massively annoyed with the obsession of making the code look exactly the same in every of its parts. Ten years ago, I could tell which of my coworkers wrote a piece of code based on its style only. It was not especially needed, given we had git (and svn before that) to tell who authored a piece of code, but it was pleasant to recognize this or that developer's style. It was not radically different styles, we were still agreeing on tabs vs spaces and how many spaces, it was more subtle. We were authors.
But now that we psychorigidly don't want to see two pieces of individuality in the same codebase, be it as syntax or sometimes even as methods preferences to achieve a task, such tool as prettier or gofmt are incredibly useful. At least, we don't waste time on that.
- tokenizerrr 9y agoWhy would you be annoyed by the avoidance of merge conflicts?
- oelmekki 9y agoWhy would developer style cause merge conflicts? We did just fine, thanks.
- tokenizerrr 9y agoWhen two people touch the same file and format it differently you get a merge conflict. Even if the actual code is identical. The only way I can imagine how you never ran into this is that either your team is tiny, or that people don't touch other people's code. Both of which are not an option as you grow.