Skip to content

Disclaimer

The short version

Everything on HighTechYeti is me talking. Just me. Not my employer, not my clients, and not any vendor whose product I’ve praised, poked at, or mildly roasted.

These are my opinions

I’m a working architect, and I write about technology the way I’d explain it to a colleague over coffee: with opinions. Those opinions are mine alone. They don’t represent the views, positions, or strategies of my employer, my clients, or any vendor or partner I work with. Nothing here is an official statement from anyone but me.

The war stories are real. The details aren’t.

When I write about an outage, a migration gone sideways, or a design review that got interesting, the lessons come from real experience. The specifics don’t. Names, industries, timelines, technologies, and other identifying details are changed, blended, or scrambled to protect the people and organizations involved. If you think you recognize your company, you probably just recognize the problem, because it’s a common one. Nobody is getting thrown under the bus here.

Not professional advice

I write from three decades of experience, but I don’t know your environment, your risk tolerance, or your compliance obligations. Treat what you read here as a starting point, not a prescription. Test things in a safe place before you try them in production, and have your own qualified people review anything that matters. “A guy on the internet said so” is a poor root cause for an incident report.

Things change

Technology moves fast, and a post that was accurate when I published it may not be six months later. Check the date, check the vendor’s current documentation, and trust but verify.

Questions?

If something here is wrong, outdated, or you just want to argue with me, use the Contact page. I’d rather be corrected than be confidently wrong.

Skip the hype. Get the good stuff.

Practical AI, security, and cloud insights from a Principal Architect's desk: sent only when there's something worth your time.

We donโ€™t spam! Read our privacy policy for more info.