We have been doomed by those best practices books

we have been seeing a huge inflow of people in the industry that have read "clean coder architecture" or simply "clean code" and as first newbies consider that on their jobs daily we can also find seniors that have this as their bibles especially when reading through pull requests or creating new features without even knowing the history of those books and the point in history they have been written. This is a major flaw, we cannot take it for granted just because someone is a famous person or the book sells a lot every single day.

Let me explain a little bit. Clean code was released in 2009, with some core elements tracing back to early 2000s late 1990s. Why?

1995. Designing Object-Oriented C++ Applications Using the Booch Method. Prentice Hall. ISBN 978-0132038379.
2000. More C++ Gems. Cambridge University Press. ISBN 978-0521786188.
2002. Agile Software Development, Principles, Patterns, and Practices. Pearson. ISBN 978-0135974445.
2003. UML for Java Programmers. Prentice Hall. ISBN 978-0131428485.
2006. Agile Principles, Patterns, And Practices in C#. Pearson. ISBN 978-0131857254.

This was the history before clean code, a bunch of stuff on an era where code development was slow, the internet was barely at 10 MB in many houses and in many countries, information wasn't spread as fast as we know and we didn't have many of the toolsets that we have right now. CI/CD, great test tools, but nothing that would help decrease software development uncertainty, and neither tools that help us contribute to the development of anything (GIT). One may argue: but github was created in 2008, yep, but people that lived in the clean code era didn't have access to it yet.