Thinking Architecturally. Lead technical change within your engineering team

This pamphlet I read from Nathaniel Schutta in the distant 2019 It was much easier to travel to foreign conferences and collect niches. Specifically in this book. 56 This only reduces the amount of water that authors usually pour into books to stretch the book. 200 - 250 pages. Specifically in this book it turned out 7 short chapters:

1. Technology Changes It's about technology changing and we can't prevent it, so we need to be able to manage it. Changes in technology often repeat themselves and we need to know the past to recognize future patterns. Here the author offers to learn from his mistakes and mistakes of the industry. (For example, the post-mortems I talked about. here)Evaluate the development of technology and do not believe in hype from conferences. Here the author even mentions the benefits of legacy skillset, using the example of COBOL:)
2. Thinking Strategically The main idea is that you need to think strategically about changes in technology and also strategically about your development. The author suggests focusing on a few areas that you are deeply passionate about and pump them. Next, the author talks about the use of techradar technologies that can be used to maintain their technological knowledge. (I've been talking more about terraces. here). Further, we are talking about structuring information flows, creating plans for their development with the creation of pet projects, personal training, group training, communication with colleagues in the industry.
3. Evaluating Pros and Cons This chapter is devoted to decision-making, how to assess trade-offs and risks. Technology Hype Cycle and Choosing the Right Tool
4. Evaluating and Choosing Technologies - how to choose criteria for evaluation, for example: documentation, community, structure of contributors, code base, testability, maturity, stability, extensibility, support, training, possibility of hiring specialists, security, getting into the corporate structure. How it can be summarized in spreadsheet for evaluation, make proof of concept and how the decision affects the policy of the organization
5. Introducing Technologies The fact that the introduction of new technology is often more difficult than its choice:) How to Mitigate Change, How to Influence Others, How to Deal with Rejections and Market Your Ideas
6. Maintaining Technologies How to maintain embedded technologies as software systems evolve. The author recalls the concept of quality attributes (Similar to architectural characteristics), which should be identified as important for a particular product, further prioritize them and use a continuous or evolutionary architecture approach with their fitness functions to track that characteristics do not float as the incremental development of the product. (Here's a little more about it. continuous architecture, evolutionary architecture)
7. Conclusion In the end, the author recommends a strategic approach to the application of new technologies to your product / project.

#Architecture #Management #Leadership #Software #SoftwareArchitecture #SoftwareDevelopment