This site exists for a fairly unromantic reason: I wanted somewhere that belongs to me. Not a profile on a platform whose layout changes every eighteen months, and not a timeline where a post has vanished after two days.

What is being built here is deliberately plain — and that is already half the point.

No build step

menzi.tech is hand-written HTML, one CSS file, and about a hundred lines of JavaScript. No framework, no generator, no dependencies, no node_modules. What sits in the repository is exactly what the browser receives.

This isn't nostalgia. It's the same reasoning I apply to solution architecture: every dependency is something that will need maintaining, updating, or repairing in two years. For a personal site with a handful of pages, a build process is not a gain but an obligation. In 2029 I want to open a file, change a paragraph, and be done — not first work out why the toolchain no longer installs.

Nothing that phones home

No analytics, no cookies, no embedded widgets. The typeface lives in the repository as a local file rather than being pulled from someone else's CDN. That leaves the site making exactly zero third-party requests — and spares everyone a cookie banner nobody reads anyway.

The most reliable component is the one that isn't there.

What I'll write about

Mostly things that actually happened in production. I have little interest in posts that summarise a technology whose own documentation already explains it better. Closer to my interests:

  • The line between standard and custom — when a custom page earns its keep, and when it is just expensive standard.
  • ALM and governance on the Power Platform: environment strategy, solution boundaries, and releases that stay predictable.
  • Integrations that outgrew plugins and flows, and the road to a decoupled architecture on Azure.
  • Pro-code in a low-code world: plugins, PCF, and the test infrastructure it takes to support them.

Company and client names stay out of it. What remains is the interesting part anyway: the starting point, the decision, and what was different afterwards.

Frequency

None. I'll write when something is worth writing about, and otherwise leave it alone. An empty blog is more honest than one filled because a content calendar demanded it.

If you have something to add — a correction, a disagreement, a better approach — I'm at david@menzi.tech.