Submitted by heartin on Mon, 09/12/2016 - 23:31
An architect should have a very good depth and breadth of technologies. Depth denotes the expertise in some technologies and breadth denotes the exposure to a wide variety of technologies and processes.
Depth or expertise in certain technologies or processes will allow you to design and develop quality systems that is scalable, secure and perform well. This will also allow you to be a better leader or mentor, and also to guide the team better in the area of your expertise.
Submitted by heartin on Mon, 09/12/2016 - 07:59
These are some tips and tricks I could gather (and continuing to gather) as part of my journey to be a good software architect.
Important things to look for while creating an architecture are extensibility, maintainability, agility, performance, scalability, standards based and feasibility.
Worlds best architectures are not the perfect ones, but the feasible ones. The architecture should be feasible enough to get implemented within the time and budget.
Submitted by heartin on Sat, 09/10/2016 - 13:35
These are some tips and tricks I could gather (and continuing to gather) as part of my journey to be a good software architect:
An architect should analyze technology and market trends and keep updated with the latest trends.
An architect should analyze the current technology environment and recommend solutions for improvement.
An architect should analyze the current processes, including continous delivery, agile etc. and recommend solutions for improvement.
Submitted by admin on Wed, 06/22/2016 - 20:42
An architect needs to have a good breadth and depth of technical knowledge. While depth is your expertise in certain area, breadth is the knowledge or exposure to a variety of different technologies and practices. This book will contain quick definitions to important technical terms and concepts that an aspirant software architect needs to know, which will help you to improve your breadth of knowledge. You may follow the links to learn deeper if you want.