About

Do it to be it.

Zyntexes is a systems administrator moving into cloud consulting, doing the work in the open. This is where that work gets written down.

Zyntexes is a cloud-consulting practice and an open notebook. The practice helps small and mid-sized businesses with Azure architecture, infrastructure as code, automation, and cloud governance. The notebook is this blog, where the reasoning behind each build gets written down so it holds up to scrutiny and is useful to someone else.

The approach

Most of the work here starts by building it badly first, then writing down the second attempt: the version with the dead ends removed and the reasoning left in. The throughline is a move from systems administration into cloud consulting, carried by real certifications and real infrastructure work rather than claims. Least privilege is the default, anything done twice gets automated, and the reasoning ships alongside the answer.

Certifications

AZ-104·AZ-900·GitHub Actions Currently studying AZ-305.

Tech stack

  • AzurePrimary cloud platform
  • PowerShellWindows and Azure automation
  • TerraformInfrastructure as code
  • BashLinux and shell scripting
  • PythonTooling and scripts

What I believe

  • Do it to be it. You become the thing by doing the work, not by waiting for permission.
  • Least privilege by default.
  • Automate what you'll do twice.
  • Show the reasoning, not just the answer.

FAQ

What does Zyntexes do?
Zyntexes is a cloud-consulting practice and an open notebook. The consulting side helps small and mid-sized businesses with Azure architecture, infrastructure as code, automation, and cloud governance. The blog documents the underlying work in public: certifications, infrastructure decisions, and the reasoning behind each one.
Who is this for?
Two audiences. Small and mid-sized businesses that need cloud architecture and automation without a large in-house platform team, and practitioners who learn best by reading the reasoning behind a build rather than just the final answer.
How do you work with clients?
Remote-first. Engagements are delivered online with no on-site requirement, which keeps the work focused on the architecture and automation rather than logistics. Scope is agreed up front so the deliverables and boundaries are clear before any work starts.
What is the blog about?
The certification journey from systems administration into cloud consulting, plus the cloud, infrastructure, and automation work that goes with it. Posts favour the second attempt at a problem: the version with the dead ends removed and the reasoning left in.
Is the writing AI-generated?
No. Articles are genuinely authored, not machine-filled placeholder content. The goal is real, verifiable experience and reasoning, which is the whole point of showing the work.
Theme