This course changed my career and entire view on software development practices at all. The word “architect” may scare you, but in my opinion it’s a mandatory course for every medior/senior developer, projectlead or (starting) architect. It gets you thinking about the development process from the first requirement till designing and constructing the actual software. It reflects on the methods we used today (based on experience at a lot of customers) and the way IDesign does it.
This course is created and given by: Juval Löwy, the founder of IDesign and a master software architect. Over the past 20 years, Juval has led the industry with some of his ideas such as microservices serving as the foundation of software design and development. Juval has helped hundreds of companies meet their commitments and participated in the Microsoft internal strategic design reviews for C# and related products. Juval a frequent speaker at major international software development conferences and published numerous articles, regarding almost every aspect of modern software development and architecture. Microsoft recognized Juval as a Software Legend as one of the world’s top experts and industry leaders.
Target audience: any architect, project lead or senior developer would benefit greatly from the class.
Duration: 5 very intense days
I went all the way to San Jose for this class and it didn’t let me down.
IDesignWhile many developers and managers have a clear idea regarding the characteristics, practices, and corresponding set of responsibilities of their roles, the picture is often vague when it comes to software architects. What is the single most important task facing the software architect? What is the division of labor and responsibilities between the architect and the project manager? How much the architecture should be tied in to the particulars of the underlying technology used, or for that matter, for the specifics of the business? Where is the hand-off point between the architect and the developers? What are the necessary skills and analysis tools employed by an architect? How do you validate the design before construction begins? How do methodologies such as service-orientation affect the design and development process? What are software architecture’s best practices, guidelines and pitfalls? How do you go about designing world-class systems? How do you make the transition from abstract design patterns and concepts to concrete development decisions? How does the architect decompose the system into its subsystems and modules?
Noteworthy is that this class is called the Architect’s Master Class (as opposed to the Architecture Master Class) because it focuses on the person behind the role, on the skills and techniques practiced by architects. The class presents the core body of knowledge required of today’s modern software architects, knowledge that transcends mere design patterns and architecture. The core body of knowledge comprises of three elements: development process, technology, and finally analysis & design. The class shows the architect how to take an active leadership role on all three aspects, as a continuum, since in order to deliver high-quality, affordable solutions, one cannot separate process from design from technology – all three have to work in concert. The class also points out classic mistakes and risk mitigations across the process, technology and design.
For more info please visit their website at: IDesign – Architect’s Master Class
My experience and short summary
[Working on it]