What are the best practices for staying current in system architecture?

Read relevant blogs and subscribe to newsletters like InfoQ, The New Stack, and Software Architecture Zone for expert insights on architecture, tools, and case studies. Explore curated content from newsletters such as Software Lead Weekly and O'Reilly Architecture Newsletter to stay updated on system architecture trends.

Learn continuously about system architecture. I personally recommend online courses and popular books. Another method I prefer is to explore publicly available architecture case studies. Being part of a community also helps immensely.

Reading a lot, both news books and source code, playing with different technologies and creating small projects all the time. That's about it :-)

1. Master the Digital Feed: Subscribe to tech blogs and podcasts for the latest trends. 2. LinkedIn Connections: Network on LinkedIn with industry influencers and join relevant groups. 3. Attend Conferences: Virtually or in person, conferences offer insights from leaders. 4. Dive into Docs: Explore API documentation for insights into emerging technologies. 5. Hackathons & Code: Hands-on experience in hackathons and open source projects. 6. Forum Engagement: Troubleshoot and learn from tech forums like Stack Overflow 7. Podcast Learning: Tune in to tech podcasts during daily routines. 8. Mentorship Matters: Find or become a mentor for invaluable knowledge exchange. Happy Architecting

Some of the best ways to stay involved with the ever-evolving technology landscape is to: 1) Attend relevant conferences virtually or in person, and interact with people there as well as attend sessions. 2) Watch online demos / tutorials 3) Many projects now have "sandboxes" where you can experiment with demos of the code / technology. 4) Build your own demos. That will allow you to get familiar with the tech at a level of detail you are interested in.

Stay current in system architecture by tuning into podcasts like Software Engineering Radio, Software Architecture Monday, and Software Architecture Podcast. Watch videos on platforms like AWS Architecture Icons Explained for insightful interviews, discussions, tutorials, and presentations by experienced architects. Learn from their stories, tips, and innovations to enhance your knowledge

Joining communities and networks in system architecture is a great way to stay current. Platforms like Stack Overflow, Reddit, LinkedIn, Twitter, and Meetup host vibrant communities where you can connect with peers, exchange ideas, and seek guidance. Participate in conferences, workshops, webinars, and hackathons to meet architects from diverse backgrounds and enhance your knowledge through collaborative learning experiences

Attend the annual US SuperComputing Conference (SC23 is in Denver this year) and join ACM. You get a subscription to the Communications of the ACM with ACM membership, and reduced SC registration fees.

Through these connections, you can access a plethora of resources, from articles and tutorials to tools and frameworks, that will empower you to stay at the forefront of architectural advancements.

Taking courses and certifications is a valuable way to stay current in system architecture. Consider reputable options like Coursera's Software Design and Architecture Specialization, Udemy's Learn Software Architecture Fundamentals, or AWS Certified Solutions Architect to update your skills, enhance your knowledge, and earn credentials that reflect your expertise in various aspects of system architecture.

Engaging in practical projects and experimentation is an excellent way to stay current in system architecture. Apply your knowledge, explore new technologies like UML, ArchiMate, Docker, Kubernetes, or Grafana, and share your work with the community. By doing so, you can continuously improve your skills, receive valuable feedback, and contribute to the field of system architecture.

Do your own blogs and newsletters and allow comment's and corrections. Create podcasts and videos, use them to learn, teach and build soft skills, communicate and manage camera fears. Build your own communities, and maintain it open, self managed, and allow any help you on grow it. Help other on their certifications. Be part of any open source community, space or project. Don't try to be owner of the knowledge, be owner of you ideas and be part and let leave the realization.

Stay hands-on and engaged in engineering work. The experience gained from actually executing the implementation of a system, feature, or bug fix is invaluable. When you're no longer practicing by participating, your skills are starting to deteriorate. If this is allowed to continue for too long, your relevance as an architect is affected as you'll no longer be in touch with the reality of your engineers.

What is written here is mostly S/W related. When it comes to systems, there are more practices to consider. INCOSE templates are one option to consider. System Engineering can be practiced even at the day to day level, with more complex tasks

I've found the structured experimentation within different frameworks to be incredibly insightful (Test-Driven Development (TDD) strategies). Utilising a framework for testing ideas—whether it’s through piloting new software tools or methodologies in controlled environments—helps us see how various components interact in practical scenarios. By systematically testing our theories and integrating feedback, we not only sharpen our skills but also stay agile.

One method of staying current is to be part of multiple RFPs and discoveries with different enterprises. You cannot afford all the latest technology experiments but can definitely derive the essence from observing what is executed in multiple projects.

Staying current in the system architecture contains a two-fold definition. On one side architecture should be upgraded according to the latest system standards like moving from monoliths to microservices or new pattern implementations whereas on the other side, needs to identify scopes for new technology introduction for more value creation. This should not be limited to system architecture changes only and include infrastructure updates as well.

The best practices to stay in current system architecture 1. Performance optimization. 2. Collaboration. 3. Documentation. 4. Automation. 5. Follow standards. 6. Security considerations. 7. Regular reviews. 8. Stay agile. 9. Continuous learning. 10. Testing and monitoring. 11. Scalability planning. 12. Version control. 13. CI/CD implementation. 14. Feedback collection.

When dealing with System Architecture, I find it important to not get lured into this never ending race for the next hype. If you take a couple of steps back, you realize that most of what is en vogue right now has its roots in the 60ies and 70ies. A lot can be learned by "going back" and learning about Lisp, Smalltalk, etc. Certainly, principles like uni-directional event flow, decoupling by message busses and other patterns have been known for decades. But keep coming back in fancy disguises like React, Microservices, etc. I always try to understand the fundamentals behind any new technology that's getting traction. It helps not only staying on top of the current developments, but also to develop a deep understanding.

As a Systems Architect there are a lot of areas one has to be versed in; - New Standards: getting involved with standards bodies with Semiconductor Companies is a great way to rub shoulders with other influencers in the industry. - Conferences: There are microcosms of technologies and you have to traverse as many as you can. Semiconductor and Software conference offer an insight to what other microcosms exist. Be aware of new bus standards, new software flow models/OS’s and hardware IP’s and Semiconductor solutions (IC’s And SoC’s). - Academic journals and research areas is a must too. Talking to Academics and Researchers is key. - Marketing: Talking to marketing/sales folk as they have a large awareness across many sectors.