/ Architect's Guide to Managing a Code Base

Description

As an architect you're often working at a high level on projects, thinking of architectural concerns such as distributed applications, CI/CD pipelines, inter-team APIs, and setting standards. Code quality affects everything that a software architect needs to work on - from a small way to a big way. We'll look at the common tasks of a software architect, as well as 3 reasons software architects should and should NOT code! We'll look at techniques and tools for managing code quality from a high and low level. Our goal as architects is to maximize the manageability of code, consider different coding paradigms and their effect on the various areas of software dev, and how to create habits and processes to ensure long term code viability. We'll take a couple of sidebars on performant vs manageable code and OO vs Data Oriented coding. We'll look at tools for doing static analysis vs dynamic analysis. These tools include Sonar Code Inventory jQAssistant ... and we’ll even build a tool using AI to do code reviews (using open source models and open source tools!

Session 🗣 Intermediate ⭐⭐ Track: Java & JVM (core frameworks & libraries, Kotlin, Scala, Groovy, Architecture)