My Architecture Journal — a place to write about enterprise and solution architecture, Data, cloud, AI, and the systems thinking that ties it all together.
Why write in public
Architecture is mostly judgement: knowing which trade-off matters in a given context. Writing forces that judgement into the open, where it can be pressure-tested. If a post helps one other architect avoid a bad call, it has paid for itself.
How frequently I write?
I must admit, I have to improve in this aspect. Many great ideas, experience, own viewpoint lives inside my brain, and not always comes out as a journal or blog. Currently aiming to write an article every 1-2 months with aim to improve in coming months.
How this site works
The site is deliberately boring in the best way:
- Static — every page is pre-rendered HTML, so it loads fast and costs nothing to host.
- Markdown in git — each post is a plain Markdown file. To publish, I write the file, commit, and push. A build runs automatically and the post appears here within a minute.
- No database, no CMS, no server — there is nothing to patch, scale, or pay a subscription for.
write post.md → git push → auto build → liveThat’s the whole pipeline. More to come.