What you’ll get
I don’t publish on a fixed schedule.
Instead, I write when there is something structural worth sharing – for example:
- architectural essays about system boundaries, context, and coherence
- technical deep dives that turn principles into executable contracts
- real-world design decisions from long-lived SaaS systems
- occasional updates around LaravelUi5 and OpenUI5 – only when they meaningfully support the ideas above
This is not a news feed.
It’s a continuation of the thinking behind the articles.
What you won’t get
- no weekly updates
- no marketing drip campaigns
- no hype or growth tactics
- no content written just to “stay visible”
If nothing important happens, you won’t hear from me.
Who this is for
This list is written for:
- senior developers
- architects
- tech leads and technical decision-makers
People who care less about tools in isolation – and more about how systems stay understandable as they grow.
If that sounds familiar, you’ll probably feel at home here.
Personal anchor
This newsletter is written by a person, not a brand.
My work focuses on designing software systems that remain coherent under growth – technically, structurally, and organizationally.
Many of the ideas shared here eventually find their way into concrete implementations, such as LaravelUi5 and OpenUI5-based architectures. But the thinking always comes first.