I have collected a lot of articles about architect competency models before, and I feel that I am not far from an architect, but when I really put this title on my head in the past month or two, I realized that I was still far from a qualified architect. I remember that during a training, a lecturer asked me the following questions:
1) Do you really have a solid development foundation? Instead of stopping at meeting project needs
2) Can you push others to improve systems or technology? Instead of stopping at DIY
3) Do you have a thorough understanding of key issues (e.g., system availability, performance, underlying development framework)? Instead of floating on the surface and not seeing the bottom of the water
4) Can you continue to put forward new ideas? Instead of just having one or two innovative ideas
5) Can you handle various affairs with three heads and six arms? Instead of concentrating on one thing
6) Can you quickly understand the problem and make decisions? Instead of hesitating and deliberating
7) Can you stand at a certain height to lead the team's technical development? Instead of stopping at dealing with trivial technical issues
Aspiring architects can try to answer the above questions. Architect is a relatively virtual position, product line architect is even more so, a department can have no architect, project manager can also lead a group of brothers to work on projects, but such a team will lack growth potential, need a competent architect to help the team improve technical capabilities, improve system quality, and get a qualitative improvement. Therefore, the role of the architect to the team must not stop at the level of quantity, which also reflects the difficulty of the architect's work.
Now every job is very difficult for me, and I am often half tired at the end of the day, but when I think about it, I haven't done anything, and my emotions are not high. But after tossing for a month or two, I slowly got a clue, and I summed it up with the following experiences:
1) Set aside an hour and a half every day for yourself not to be disturbed and do the most urgent and important things of the day
2) Plan your work according to different time periods, and do things according to the plan without messing up
3) Maintain a good attitude and learn to be a person first
4) Lower your posture and maintain the learner's attitude
5) Relax the scope of attention to facilitate the development of ideas
6) Start with practical things first, and gradually increase the height and expand the scope
In short, the work of an architect is far more difficult than expected, but now that I have taken this step, I can only bite the bullet and go on, no matter what the achievement is, this is also a very important experience in my career, what I have to do is to go all out to experience, so I feel a lot easier to think about it, nice
|
Posted on 5/31/2017 9:58:34 AM
|
|
|
Posted on 5/31/2017 11:12:55 AM