I'm not an architect, just an engineer.
>An issue I have right now at work is that the business people don't even really understand the tool or business domain fully, so when they ask for features, it is left to us to figure out if it makes any sense. I've had this happen before with clients not knowing what they have and what they want. Of course this impacts the initial domain understanding and chaos ensues shortly after.
in that case I think requirements analysis is the step that needs more work. No architectural method can work with unclear requirements, and unfortunately clients are indeed known to change their minds about stuff. Requirements is sort of a different topic though which probably deserves its own thread.
Personally i'm glad i learned architecture, if only to do better in system design interviews. I've designed a few small systems in a work context but nothing at ""scale"".
Especially now in java shops they're starting to do all kinds of hardcore system design interviews that require you to know a myriad of on prem and cloud middleware/esb tools (muh apache artemis/apache camel/kafka/rabbitmq/mulesoft/aws kinesis) and integration+SOA patterns, I think the age of leetcode is passing and the age of "muh system design" is coming, esp. for non juniors.
In any case most people, be they architects, software engineers, or even related such as sdet/devops/etc, can benefit by learning some architecture. Its only learned by either years on the job (and even then only if you have relevant work experience, not maintaining one legacy app for example). OR you can take a shortcut and read some of the books ITT and level up without having to spend 25 years working on different systems.
IMO its sort of the missing link in software development education, unfortunately most CS programs(undergrad or grad) don't teach it and most undergrad SE programs (that exist) don't include it either. It's generally only taught in advanced degrees in SE (at least in the US), which is a shame because its literally useful for every software engineer and devops person.
PDF-REL is the original DDD book for anyone interested.