Daniel mohl is a Professional Software Engineer/Architect who is interested in understanding various complex programming languages, enterprise application architectures, and how to build businesses and technologies, he is familiar with F #, C #, coffeescript, JavaScript, Erlang, Asp. net, MVC, WPF, WCF, sliverlight, SQL Server, and other technologies. Has many years of software development experience.
He is often asked by potential and promising programmers: "How can I become an architect ?" To be honest, this is already a common topic. The answer is of course based on the situation. However, based on his own experience, he also provides some suggestions and materials to help you quickly embark on the path of architects.
The following is a list proposed by Daniel mohl for your reference:
First, you must constantly seek to improve and improve yourself. The best way to improve myself is to read the following books, which greatly improves my software architecture skills. We recommend that you:
- 97 things software architects should know
- Enterprise Application Architecture Model
- Agile Software Development, principles, models and practices
- Enterprise Integration Mode
- Javascript language Essence
- Use legacy code to work effectively
- Domain-driven design
- Enterprise Architecture Policy
- Design Mode)
- The
Goal
- SOA Design Model
- SOA
Principles of service design
Besides reading, what else do you need to pay attention?
- Learning a new language every one or two years, F # is a good choice.
- Select a key area, but try to have a high-level understanding of many technologies.
- Activate a blog for the key areas you are interested in and expand your knowledge in this area to gradually become an expert.
- Deal with different technologies, programming languages, design patterns, structures, and so on (even if it doesn't directly help you in everyday life. You never know whether this knowledge will be useful in the future, but it is definitely beneficial to you.
- Talk about "language" based on your target audience ". As an architect, you will deal with people of all levels and have different technical understandings. Therefore, you must learn how to adjust your explanation, so that they can understand it.
- Read blogs, watch/attend Twitter or G +, listen to podcasts, read magazines, attend user group meetings and technical meetings, and actively speak at these meetings. These will bring you endless knowledge and fun, build your own "brand" and provide communication opportunities.
- Discipline is the key. Always do your favorite job, even if it sounds less interesting. Schedule time to learn new things every day, even 15 minutes. Never be occupied by other things.
- Start your blog journey. I found that writing down things will give you a deeper understanding than reading.
- Take advantage of the "leisure time", during which you can read this magazine or listen to podcasts.
- Understanding various available development tools can make the architect's work better and more effective
- View the architecture of many different projects
- Learn how to manage each project
- Learn some evaluation techniques to provide valuable evaluation for the business
The list above is summarized by the author. Although it seems boring, it is a lot of fun throughout the software development process. If you have better suggestions, please share them with us.
