Chief Architects or Consultants or Solution Architects will be interacting with various teams, technology, and business leaders, and other stakeholders. Providing Point of Views or introducing yourself in a concise manner or quoting words or sentences with short explanations are some of the skills an Architect should possess. This post is designed to highlight some of those “Architect Quotes, Skills, Point of Views” and I recommend Bookmark this because I will keep updating this page.
Assuming an Architect has knowledge on various Architecture styles, Patterns, Architecture Characteristics, first let us start with a popular quote –
Consider thinking of architectural decisions as to investments and take into account the associated rate of return, it is a useful approach for finding out how pragmatic or fit for purpose every option on the table is.
– Richard Monson-Haefel, 97 Things Every Software Architect Should Know
It’s Not What You Say, It’s is How You Say It
| 1 |
Introduce Yourself |
I have been developing software for a long time since back in 19xx or 20xx Since then I ended up working in different technologies including Java, .Net, Cloud, Sharepoint, Python, Machine Learning, Databases, Business Analysis, Testing etc. I worked and used various platforms, tools, frameworks etc. Then in the year 19xx or 20xx, I started doing “Cloud/Big Data/EJB/Machine Learning/Data Science/Architecture/Business Architecture/Program Management/Engineering Manager/Consultancy that evolved into supporting multiple clients and it was pretty exciting Specifically, in the past ‘x’ years, I pretty much “focused on” “X” Architecture Styles, travelled world, worked with various clients helping them in understanding and adopting those “X” Architecture styles and their associated design patterns. |
| 2 | What keeps you exciting |
Throughout my career I have been always in emerging and “main-stream languages, technologies, platforms, paradigms, architectural styles, frameworks” Above could be related to “software development” or “software deployment” or “software infrastructure” I followed industry leaders who are thriving in making “software development better”. While above leaders are focusing on betterment in software architecture, development and delivery, I focused on “how to make those leaders innovative approaches reachable to the enterprises through consulting and teaching”. I think I am very successful in doing it with various clients consistently and uniquely. I always wanted to be an “early bird” person and make Emerging technologies and Innovative Ideas adoptable, that keeps me interested and excited because they need constant learning, experimentation and being ready way ahead of mass adoption by software engineers and businesses. |
| 3 | What Architecture Style or Design Patterns we should adopt? |
If you are thrown with this question randomly, then simple answer is For this I recommend readers of this post to study a book released in the year 2020, “Fundamentals of Software Architecture” by Oreilly Above book has a fantastic diagram that highlights “Architecture Styles”, “Architecture Characteristics”, “Design Patterns”. I strongly think Software Architects should master that diagram well |
| 4 | What are the rules of a “Software Architect” |
The rule of an architect is – “understand the context in which they are building the software application” and “pick the right architecture for their application” Instead of picking with stereotype of thinking, like “Data Lake Architecture”, “MicroServices Architecture”, “MVC Architecture Pattern”, “Streaming Platform”, “Distributed Computing” etc. Based on my research and videos watched, I learned that “no architecture style should be a popular choice by default“ Also, just don’t throw the “Design Patterns” quite “liberally“ Instead, open up a conversation with the project stakeholders, highlight various “design choices” and “good and bad” with each of those choices |
| 5 | What is the future of software or IT? |
We all need to understand that, “software eating the world“ That means, in every industry software is an integral part of their business. Every product or service in various industry is powered by software So as a practitioner, developer and consumer of software solutions, I think the future of IT we should focus is, “how to make it better in its architecture style, adoption, learning, development, delivery and value proposition“ |
| 6 | What aspects you generally observe in prima-facie of any Software Architecture | 1. Modularity 2. Cohesiveness of each module that covers business domain functions in the context 3. Loose coupling between the Modules 4. Flexibility in evolvement of module(s) according to business needs without major disruptions 5. Good story on trade-offs taken during architecture creation |