![]() ![]() I went roughly from mainframe developer to client-server C/C++ developer to Java/JEE developer. As IBM transformed, I had to do the same. I quickly learned that technology moves at a really fast pace, and I had to keep up. I loved writing code back then, and I still do.Īt that time, I really thought that I would be a mainframe developer for my entire career I enjoyed it that much. I learned how to develop software that ran on the mainframe, and I thoroughly enjoyed it. When I joined IBM as an intern in 1992 while studying computer engineering at the University of Toronto, I joined a small IBM team as a developer. Mike Nitsopoulos, SVP strategy & innovation, Retail Banking Technology, PNC Bank This is why architects need technical breadth to be able to best guide the technical team on implementation choices." If you ask the mainframe team to build an API, they will build you the best COBOL API you can imagine. If you ask the Kafka team to build an API, you will get the best API built on Kafka you can imagine. For example, if you want to build an API and you ask the Pega team to build it, you will get a Pega-implemented API. "We need to avoid building solutions grounded in the expertise of the team you ask. But in my opinion, these are two key traits. There are many other traits, and it would be difficult to order them in terms of importance. I not suggesting that these are the two most important traits for enterprise architects. They also need to keep up with technology as it continues to move rapidly. First, after I published Launching and scaling a transformation organization, one of the technical leads from a client where I led a large transformation as chief architect reached out and reminded me that one of the key reasons things worked out well on that transformation project was because the architects were hands-on.Īnd more recently, I've found that architects who don't have technical breadth (that is, they are focused on one technology) create architectures that leverage the technology where they are an expert, even if there are far better solutions using other technologies.Īrchitects need to have technical breadth and be hands-on. Architects need to have strong communication skills.Ī couple of recent events have prompted me to write this article.We discussed the following important traits of the agile architect, regardless of their architectural discipline: The architect sets up fences within which the teams work. In The role of an agile architect, Kyle Gene Brown, Darcy Lalor, and I talked about the architect's role being that of a boundary setter. Their criteria is similar to Peter Eeles' list. Mark Richards and Neal Ford have a section on the expectations of an architect in their book the Fundamentals of Software Architecture. The architect is aware of organizational politics.The architect has technology knowledge.The architect has knowledge of the business domain.The architect understands the software development process.How to explain modern software development in plain English.The automated enterprise: Unify people and processes.How to become a Red Hat Certified Architect. ![]()
0 Comments
Leave a Reply. |