So, in your opinion are Clean Code and Clean Architecture still relevant/updated?
I've come more interested in the way I think about/produce code in the last couple of months and am searching for something that might be a good read on it - considering I'm mainly a JavaScript developer.
I find that most of the concepts of SOLID, for example, are really hard to figure out in most of the code base of the projects I've worked/see online implemented in Node for example. It might be related to my lack of knowledge and understanding of said principles though, but I've seen a youtube video (https://www.youtube.com/watch?v=CnailTcJV_U) some months ago that showed me a "clean architecture" implementation that I've never really seen in any project I've fiddled with.
In my opinion, the caveat on the article is very apt: Clean Code teaches rules, not principles. If you read it with a critical mind you'll get a lot of it, if you follow it blindly you'll get a lot of bad habits. Unfortunately programmers need some experience to be able to do it.
IMO the same caveat applies to Clean Architecture: it is study material to architects, rather than something you can copy-paste into a new project. The reason it's dauting, IMO, is because there are some unnecessary concepts there that are unrelated to the "grand idea", and those small things might make sense for Bob Martin but might not make sense to you.
If you want to understand it, I really like this article. I think it explains very well the "grand idea" of architectural templates like Clean/Hexagonal/Onion... and links it to Gary Berhnardt's Imperative-shell-functional-core: https://danuker.go.ro/the-grand-unified-theory-of-software-a...
