The notion of clean code was introduced through Robert Martin's book. Nevertheless most of the time clean code is often a set of conventions that are specific to each ecosystem (with foundations sometimes common to several languages).
For example, naming your variables correctly is rather common sense (personally, I was already doing “clean code” before knowing the very notion of clean code).
However, you have to understand that you should not stupidly apply these rules without taking into account the context or even the opinion of your team. It is now not uncommon to see tools like SonarQube appear that will recommend following patterns for the sole purpose of giving you a "positive" rating.
Other links that I recommend you read:
- [Clean Code (Wiki C2])](https://wiki.c2.com/?CleanCode)
- Effects of Clean Code on Understandability
- The Effect of Poor Source Code Lexicon and Readability on Developers’ Cognitive Load
- It's probably time to stop recommending Clean Code
- Clean Code JavaScript (github)
Fairly recent conference;
- Clean Code - Uncle Bob / Lesson 1 (there are several videos 1, 2, 3, 4, 5, …)
⬅️ 🌇 Architecture & Paradigms: Documentation | ➡️ 🌇 Architecture & Paradigms: Object Oriented Programming