Writing Clean Code means adhering to a set of principles which by the way have existed for a long time before Uncle Bob wrote a book about them. All of these principles make sense in certain contexts and it is important to understand them. But that's only the easy part.
The hard part is:
Some of the principles are highly subjective: What is a single responsibility? What is a meaningful name?
Some of the principles do not go together very well, especially when you overdo one of them. For example, removing duplicate code (DRY) often creates additional dependencies (coupling).
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.
Writing Clean Code means adhering to a set of principles which by the way have existed for a long time before Uncle Bob wrote a book about them. All of these principles make sense in certain contexts and it is important to understand them. But that's only the easy part.
The hard part is:
Some of the principles are highly subjective: What is a single responsibility? What is a meaningful name?
Some of the principles do not go together very well, especially when you overdo one of them. For example, removing duplicate code (DRY) often creates additional dependencies (coupling).