Why this exists
Learning in public, on purpose.
Most IT documentation is written after everything works, by someone who’s forgotten how confusing it was at the start. I write while it’s still confusing. Every note here starts as a real problem in a real environment — an ASR rule that broke printing, a break-glass account that wasn’t, a policy that looked right and wasn’t applying — and ends with what actually fixed it.
I don’t claim to be the expert. I claim to be the guy who did it last week and wrote it down. If you spot a mistake, tell me and I’ll fix the note and credit you.
I don’t claim to be the expert. I claim to be the guy who did it last week and wrote it down. If you spot a mistake, tell me and I’ll fix the note and credit you.
Built with AI
Yes, AI helps build this site.
I’d rather say it than have you wonder. I use AI tools (Claude, mostly) to help design and build this site, to tidy up my drafts, and to sanity-check scripts before they touch a tenant. The problems, the testing, the screenshots, the mistakes and the opinions are mine — every note is something I’ve actually done, and I edit everything before it goes live.
I think that’s where IT work is heading: admins who know their environment, working faster with AI alongside. This site is me practising that in the open.
I think that’s where IT work is heading: admins who know their environment, working faster with AI alongside. This site is me practising that in the open.
Right now
What I'm working on.
Studying
CCNA
Rebuilding my networking fundamentals properly — expect Networking notes to pick up.
Building
Admin Basics LLC
Weekend consulting for Salt Lake small businesses that need Microsoft 365 done right.
Writing
One note a week
That’s the goal. Some weeks it’s a deep dive, some weeks it’s a fix I don’t want to forget.