I think you're still missing the point. Knowing system architecture is not more important than knowing how to read/write code efficiently, specially when you're

I think you're still missing the point. Knowing system architecture is not more important than knowing how to read/write code efficiently, specially when you're not designing systems most (if not any) of the time. If you can't do that latter, you most likely can't do the former... this article is good advice for those who need it... once you know those things, you will have a much easier time learning higher level concepts and software architecture - and I, unlike you, find that those are actually the large majority of articles as they're, paradoxically, easier to write as you can bullshit your way through buzzwords and make empirically unverifiable outlandish claims about "microservices", "serverless", "blockchain" or whatever else may make you sound smart, without actually providing anything of real value.