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...

Of course I also recommend Imperative-shell-functional-core itself: https://www.destroyallsoftware.com/talks/boundaries