About this series: People at conferences, training, and meetups often ask me what I would recommend learning X or Y. I’m always happy to give some suggestions depending on the person’s experience level. Unfortunately, this doesn’t scale very much, so
Technical debt? Who cares?
Why assessing inner software quality is bad for decision-makers (and why customers don’t care anyway…).
Checking Architecture Governance with jQAssistant, Neo4j and Jupyter
Introduction Software architects have to make sure that the communicated software architecture blueprints exist in the real world. For this, manual inspections as well as automated measurements are needed to avoid surprises. In this notebook, I want to show how
Announcing the cards42 project!
cards42 provides some hands-on cards about various topics on software architecture. We’ve created and printed the first 16 cards (of 42) that help software architects and there like in their daily business.
Michael Nygard – Architecture Without an End State
Michael Nygard (author of the famous book “Release It!”) gave a talk about the steadily evolving nature of software architecture of a software system (and how to “surf on the wave of change”). Core problem There will be always a