One of my friends hosted a rather excellent Lunch and Learn session today, talking about the benefits of Clean Code, and referenced a book by Robert C. Martin, named: -
Clean Code: A Handbook of Agile Software Craftsmanship
We had a good debate about the advantages and disadvantages of comments in code, given that we can / should have self-describing variable and function names.
The debate continues apace; my personal view is that comment should serve to describe WHY I did something, rather than HOW and WHAT, which absolutely should be self-describing.
I'm thinking about this from the perspective of future support i.e. "Why did Dave do it that way ? Oh, because time was short, or Stack Overflow was down, or the code wasn't intended to live forever"🤣
Meantime, my friend, Aiden, has written a much more well-informed piece here: -
Practising Clean Code in Node.JS
Go read, and let the debate continue .....
Clean Code: A Handbook of Agile Software Craftsmanship
We had a good debate about the advantages and disadvantages of comments in code, given that we can / should have self-describing variable and function names.
The debate continues apace; my personal view is that comment should serve to describe WHY I did something, rather than HOW and WHAT, which absolutely should be self-describing.
I'm thinking about this from the perspective of future support i.e. "Why did Dave do it that way ? Oh, because time was short, or Stack Overflow was down, or the code wasn't intended to live forever"🤣
Meantime, my friend, Aiden, has written a much more well-informed piece here: -
Practising Clean Code in Node.JS
Go read, and let the debate continue .....