Great comment! Thank you!
In my article, I paid more attention to skills that are a must, but I did not cover the field of knowledge collaboration fully (which is, of course, an utmost important, and I've mentioned it). Another point, that the teaching and collaboration is mostly the tech lead field. I completely agree with John Van Wagenen who wrote dev.to/jtvanwage/a-common-technica... - that is about sharing and collaboration. But the duties of a software architect (in a perfect world, of course) includes all those things I wrote, so he or she is not obliged (and even don't have time) to teach let's say a Ruby programmer, how to choose a software development methodology. If the software architect will spend the time on this, the project will unlikely be completed successfully. This is the matter of the obligations and productivity. So, definitely, a software architect should be a mentor, but the most important for this specialist is to be a real professional who can architect, carry and successfully complete the project with minimum time and maximum profit.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.