Notes on software architecture, cloud computing, and homelab.
CQRS isn't just "separating reads from writes" — it's accepting that, for an instant, different parts of your system will disagree about the truth. When that trade-off is worth it, and when it's over-engineering.
Suggestion for @microsoftteams : Add a "mute" button for a specific person in a meeting, but not for everyone, just for me, so that whatever they say I don't hear it. It's a need that not only I might have
“Everyone has two lives, and the second one begins when you realize you only have one”
You don't need to be an ML engineer to make good architecture decisions with AI. The minimum concepts every architect should grasp before putting a model into production.
Code tells you what the system does. It almost never tells you why it was decided to be built that way. Architecture Decision Records are the simplest way I know to not lose that second part.
“Anyone can build something complex. It takes a good architect to keep it simple.”
