Building Evolutionary Architectures • Rebecca Parsons, Neal Ford & James Lewis • GOTO 2023

[@ks1970in]

Meilir Page-Jones - what a great author, the "Practical Guide to Structured Systems Design" - is one of my career defining books, the clearest taxonomy and examples of coupling and cohesion that one can ever find. The concerns remain - whether OO (which methods belong to which class) or micro-services (what is the API of my service), applicable many other contexts.

[@br3nto]

39:32 of course you can evolve a ball of mud. It requires lots and lots of refactoring to make it testable and verifiable so that pieces of code can eventually be decoupled and isolated. Unless you want to scrap the software and start again, balls of mud have to evolve.

[@br3nto]

25:13 I don’t understand why you’re making a distinction between “architect” and “developer”. They should be one in the same. Both roles done by software engineers, and both always in the same meetings. How can you create good systems if you create a separation between architecture design and software design??? I get that you can have one software engineer working on the architect, and another on features that leverage that architecture, but the development requires such close communication and coordination. It’s like when our network engineer was asked to architect a software solution…. The architecture was all wrong for a software point of view. It sounds like something in this talk is a bit out of step with the needs of reality