[sdevonoes]

I think there is no other good alternative to learn about real-world software architecture (besides working experience, of course). Most of the books about the topic focus on theory and "happy" patterns. Once you have read those books one lacks total touch with the real world and how architecture is applied in real software.

[ahartmetz]

I think the biggest mistake that novices make is to use "as much architecture as possible" instead of "as little architecture as possible". Architecture and design patterns should be used once you have a problem to solve where they fit well, not a priori / because they seem cool and interesting. (Of course, many err on the side of no organization as well.)

[niwork]

How relevant is architecture for someone like me - a 5-10 years of experience dev who has worked in non-managerial developer positions in small teams.

When I look at architecture patterns I feel so much of it is aimed at enormous projects, in which case I think you need actual experience of working in an enormous project alongside others from whom you can learn rather than just reading it from a book.

And there's so much difference between them.. which is the "right" one? Is Robert C. Martin's "Clean Architecture" approach right in condition X, or some other approach in condition Y?