Our work with software is a system of systems, comprising technical systems (software, hardware...) and social systems (users, business, teams...). For decades, our primary focus has been on the quality of technical systems. Social capacity (agile, kanban ...) is often perceived as a support for producing software, a means to an end. 

When complicated software systems take on more complex traits in a sociotechnical entanglement, software design need to be evolved from a craft of mechanistic…

Creating high-quality software is challenging due to a focus on solutions over understanding organizational context. Developers need to engage with stakeholders across contexts. However, stakeholder communication can lead to misunderstandings and conflicts, disrupting knowledge sharing. This often results in autocratic decisions by architects. Achieving sustainable and design decisions, it's more effective to employ visual techniques, improving collaboration with stakeholders.

This talk explores…

Disclosure - this is a talk about people - not about AI. This is a talk about how we will continue to apply our humans strenghts in a world enhanced by AI.

One of the LLM engines I work with seems to think it can take over my job as an architect. I say with some confidence that for the next few decades, my job will be heavily influenced by AI, but not replaced by AI. For example I am presenting and OOP and *it* is not.

Software architects and system architects will not be replaced anytime soon…