Apple at scale
I run Jamf Pro for a large higher-ed fleet. Profiles, policies, packages, Self Service, Apple Business Manager. If it only works on the test Mac, it is not done.
I manage Macs in higher education. A large mixed fleet: Jamf Pro, identity, packaging, patching, and the security tools around them. If something should not be done by hand, I automate it. And I leave something the next person can actually use.
AI is part of the work. I use it to get a first draft down, debug something weird, check my own work, and automate the stuff I do not want to do by hand. It gets a script or a writeup started. I check that against the fleet before it goes anywhere.
Documentation is a deliverable. If a change only lives in my head, it is not finished. I want work I can roll back, scripts a teammate can read, and systems that do not depend on whoever remembers how it was done.
I run Jamf Pro for a large higher-ed fleet. Profiles, policies, packages, Self Service, Apple Business Manager. If it only works on the test Mac, it is not done.
Shell and PowerShell, when clicking through it is the wrong tool. Logged, readable, something a teammate can run without guessing what I meant.
Platform SSO and modern sign-in, set up so it still makes sense to the person at the Mac.
I took the Jamf Pro track in order this year. Associate in February, Tech in March, Admin in April, Expert in July.
Earlier: CompTIA A+, December 2018. // B.S. in Cybersecurity, finished while I was a stay-at-home dad with my oldest.
Away from work I self-host what I can, mess with mesh radio, and build small apps when I want to see if an idea holds up. dc-pulse is a native iOS app for watching what is changing across D.C.
I read science for the edge cases. Physics, astronomy, evolution, the kind of systems where simple rules do something weird. I enjoy retro games, books, space stuff, and sometimes a beer. I care more about how a thing fails than about the tidy summary.