TLDR: Architects get relatively few opportunities to practice their craft, so we will group up to formulate architectural visions for “real world” business problems. Attendees will then evaluate each group’s solution to gain insight into the pros and cons of different approaches.
Fred Brooks said, “How do we get great designers? Great designers design, of course.” So how do we get great architects? Great architects architect, but architecting a software system is a rare opportunity for the non-architect. For this, we turn to an ancient tradition, born of the martial arts, designed to give the student the opportunity to practice more than basics in a semi-realistic way. The coding kata, created by Dave Thomas, is an opportunity for the developer to try a language or tool to solve a problem slightly more complex than “Hello world”. The architectural kata, like the coding kata, is an opportunity for the student-architect to practice architecting a software system.
In this workshop, attendees will be split into small groups and given a “real world” business problem (the kata). Attendees will be expected to formulate an architectural vision for the project, asking questions (of the instructor) as necessary to better understand the requirements, then defend questions (posed by both the instructor and their fellow attendees) about their choice in technology and approach, and then evaluate others’ efforts in a similar fashion. No equipment is necessary to participate–the great architect has no need of tools, just their mind and the customers’ participation and feedback.
In the tech world, diversity isn’t just about backgrounds; it’s also about how we think and process information. ADHD and Autism Spectrum Disorder (ASD) are often pigeonholed as challenges. However, what if we told you that these so-called ‘disorders’ house superpowers that can be game-changers in the realm of coding and software development?
Join us as we delve into the remarkable abilities often associated with ADHD and ASD – like laser-sharp focus, unparalleled attention to minutiae, and a natural flair for discerning patterns. More than just a session, this is a call to action: to shift our industry paradigm from focusing on perceived deficits to recognizing and leveraging these neurodiverse strengths.
During this session, attendees will:
– Gain insights into how traits associated with ADHD and ASD can be massive assets in the tech and coding environment.
– Learn strategies to nurture and harness these neurodiverse strengths, creating a more inclusive and effective workplace.
– Challenge and reshape their perceptions about neurodiversity, emphasizing a strengths-first approach.
As a consultant, I get to see many systems built by many different developers. Recently, I’ve seen an uptick in the number of systems built with a microservice architecture in mind, but those systems often include a lot of the same mistakes that keep them from working well.
In this session you’ll learn from my experiences and get pointers on what to avoid in your microservices implementations so that you don’t accidentally build something which has all the worst aspects of a monolithic application and the worst aspects of microservices These monsters are what I call “distributed monoliths”, and I can help you avoid building one accidentally.
If you currently have a controller-based API built in ASP.NET or ASP.NET Core, you might be eager to embark on the journey of transitioning it to a Minimal API approach, but not know the best process to make it happen. If so, this talk is tailor-made for you.
We will delve into the advantages of using Minimal APIs, including the simplification of complexity and the boost in performance. We’ll also go though a methodical, step-by-step migration process, complete with illuminating code examples so you can see the process in action.
By the end of this session, you’ll be well-equipped to update any of your ASP.NET or ASP.NET Core APIs from controller-based code into the realm of sleek and effective Minimal APIs.