Have a well defined standard for both structure and formatting of code in your project that helps with readability for as many people as possible, and stick to it.
Having a specific standard of coding is good
It helps as one learn new things, that's what CleanCode is all about(adopting the best practices)
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
I probably should have been a bit clearer, but what I meant was that it doesn't have to be the same standard as what CleanCode puts forth, as long as you have some standard that you're sticking to which doesn't make the code particularly hard to read.
I see far too many people getting hung up on a specific coding standard instead of just figuring out what works for their project, and as a result they spend lots of time jumping through hoops to meet the coding standard when their existing code was perfectly readable.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Having a specific standard of coding is good
It helps as one learn new things, that's what CleanCode is all about(adopting the best practices)
I probably should have been a bit clearer, but what I meant was that it doesn't have to be the same standard as what CleanCode puts forth, as long as you have some standard that you're sticking to which doesn't make the code particularly hard to read.
I see far too many people getting hung up on a specific coding standard instead of just figuring out what works for their project, and as a result they spend lots of time jumping through hoops to meet the coding standard when their existing code was perfectly readable.