What do you do if you're a system architect and new technology is overwhelming?

Staying informed amidst constant new tech influxes requires a structured, focused learning approach. Prioritise technologies directly impacting current projects or long-term organisational goals - depth over breadth. Allocate dedicated learning time slots, protecting them diligently from competing priorities. Collaborate and share expertise across teams and professional circles. Cultivate a growth mindset - embrace continuous learning by exploring new tools/approaches and challenging assumptions. By prioritising relevance, curating sources, scheduling learning, collaborating widely, and fostering a growth mindset.

Most of the time, the sponsor couldn't care less about the latest technology so long as whatever we use works. Smart sponsors know that costs are high at the bleeding edge - what did the Apollo project cost? The only reason the Pope cared what type of paint Michelangelo used on the ceiling was that the did the background in cobalt blue, the most expensive paint known to man then and now. He blew the entire budget painting the background. The right approach to overwhelming new technology is to ignore it. How many "shiny new things" have come and gone? You have to let it mature a bit unless your sponsor doesn't care about cost. "Be not the first by whom the new is tried, nor yet the last to cast the old aside."

Stay informed over the new new techs coming and building around which will keep you updated, try to follow some geeks which share the updated contents and hand-on explanation for the same

In handling overwhelming new technology, system architects must adopt a methodical learning strategy. This involves setting aside dedicated time for comprehensive research, prioritizing technologies relevant to ongoing projects. Active engagement with curated resources, such as newsletters and professional networks, is crucial for staying updated on industry trends and insights. By focusing on mastering core concepts rather than superficial knowledge across a wide range of technologies, architects can make informed decisions and effectively address project challenges. This structured approach empowers architects to navigate the complexities of new technology confidently, contributing to project success and career advancement.

Evaluating relevance hard - few innovations are used in the way the originators anticipated. How many inventors realized much income? Goodyear and Singer died broke; money was made by businessmen who made the ideas commercially practical. I was hanging around MIT when getters and setters were discussed. Information hiding would let you change the implementation of a variable and users wouldn't know. If you changed weight from pounds to kilograms, for example, the original getter and setter would convert on the way in and out and a new getter and setter would handle the new units. Sounded plausible. NEVER in the 50 years since then have I seen that happen. Getters, setters, and information hiding sounded good but were irrelevant.

Every innovation is hyped WAY beyond reality. Hands-on is the ONLY way to separate hype from truth. Problem is, most places, the only way a developer can rise in the ranks is to go into management. Sharp-elbowing to a level high enough to make decisions about new technologies takes long enough to lose touch with what's really going on. You have to code for production 2 or 3 days a week to stay in touch and no manager I know does that. Technology decisions made by Upper Management are inflicted on lower ranks whether they're suitable or not. Developers catch steaming blobs of Bewilderment dropped from On High and roll them and pat them into Business As Usual. Bewilderment to BAU is a major factor holding back innovation.

I believe that collaboration and sharing are crucial factors when dealing with new technology. No one can know everything, and when faced with the complexity of new technology, combining knowledge and experience from various sources is essential. Sharing knowledge with colleagues and seeking support from those experienced in the new technology field will help you progress further. Participating in communities or forums is also a good way to learn from different perspectives and viewpoints, thereby gaining a better understanding of complex innovations. By sharing challenges and solutions, not only can you reduce the feeling of overwhelm, but you and your team can also advance further in enhancing shared knowledge and skills.

"The Architect" need not (should not) be a guy in an ivory tower who serves as the gatekeeper for all major design decisions. "Architecture" is one of many skills needed on a development team. One or more team members should have Architecture as a "deep" skill and others may have it as a broad skill. The team member that is deep in Architecture may be weak in Kubernetes, while another team member is deep in Kubernetes. If an emerging architecture involves Kubernetes, these two team members should collaborate. Not only will these two team members both grow, but the team will have more redundancy in its Skills Inventory.

There can be times when the technology becomes overwhelming. But one should always keep in mind that the basics remains the same. Perform repeat and rinse approach until you are confident over the technology and try relating it with the basic concepts to understand complex relations

Relate new technology to things you already know. Try and understand deeper architectural patterns that underpin multiple products and technologies. Focus on _why_ something works the way it does, not just what functionality it provides. This reduces the learning effort over time.