1. A good architect must be a good programmer
-
I haven't written code for N years, how can I guide the country?
-
I haven't done N years of architecture practice, how can I guide you to avoid pits?
-
Only the framework, no details, how to convince the public?
bad case: the project failed, and the architect commented that the technical team was "poor"
bad case: The project failed, and the technical team commented that the architect "will only fool"
2. Cross-domain knowledge
-
If only one direction is strong, it is at most a technical master.
-
In addition to experts in one/several directions, it is necessary to understand many aspects such as peers, sites, services, data, etc.
-
Have an understanding of R&D, testing, operation and maintenance, and security
-
In addition to technology, you must have an understanding of business, products, and project management.
Voice-over: Dedicated to one direction for 10 years, is it good or bad, it is worth discussing?
3. "Speaking clearly" is a very important skill
-
Know how to abstract and simplify complex things
-
Know how to visualize and concretize abstract things
-
Know how to put images on the whiteboard and draw them
-
Know what to say on the whiteboard
bad case: some architects, they know it, but can't explain it, it's a pity.
4. Landing ability, communication ability, execution ability
-
It's not enough to say it clearly, it's the real effort to be able to implement it on the ground
-
The same is a technical person, communication should not be bossy, giving orders
-
Don't talk about the high-level nouns every day, what's on the ground is the value
Voice-over: How often do you hear these terms lately? Blockchain, Cloud Computing, Saas. Be careful, any architecture design that is out of business is a hooligan.
Have you seen the big win on paper?
—————END—————