TNT

Introduction 

Welcome to the ArchitectHer “Technical, Not Technology” (TNT) series.  It's a forum for the community that focuses specifically on the technical aspects of “doing” good architecture e.g. use of principles and patterns, and not technology specific topics like “how to build microservices using vendor-solution X”. 

We hope that you’ll be able to be a part of this initiative – bringing your expertise and experience and using it to help facilitate fruitful conversations amongst participants.  

Got an topic you'd like us to cover?  Let us know!  Contact us at events@architecther.co.uk 

Past Sessions

Estimating you Solutions Technical Operating Costs

Presented: 26-May-2026 | Adrian Kearns

Slides and supporting material: https://morphological.wordpress.com/2026/05/26/estimating-you-solutions-technical-operating-costs/ 

Abstract: A solutions financial costs are often key for senior decision makers, but architects and technical staff often neglect them.  Establishing your systems base-line activity (transactions, throughput and storage, etc) makes it much easier to take vendor price lists and model out likely costs. 

What's in it for you: Give yourself, and your non-technical stakeholders confidence, by providing realistic cost estimates using calculations that are transparent and defensible.  With this simple process you'll be able to take the guess work out of estimates, break-down complexity, and easily alter forecasted costs as details change. 

Architecting for Change 

Presented: 24-Mar-2026 | Adrian Kearns

Slides and supporting material:  

• https://morphological.wordpress.com/2026/03/24/tnt-architecting-for-change-presentation/

• https://morphological.wordpress.com/2026/03/30/architecting-for-change-series-intro/ 

Abstract: Object Orientated design principles such as SOLID, and concepts like Cohesion & Coupling, help create applications that are better able to withstand change over time.  These ideas scale to any level of abstraction, making them essential tools for guiding architectures.   

What's in it for you: By using them correctly you can isolate dependencies and manage complexity, making your day-to-day work smoother and your architectures more effective and long-lived.  They are also great for cutting through marketing spin, technical misdirection and architect better solutions - your superpower for cutting through bs.