<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>the human engineer on hmn</title>
    <link>https://the.hmn.engineer/</link>
    <description>Recent content in the human engineer on hmn</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>mike@hmn.engineer (michael meyer)</managingEditor>
    <webMaster>mike@hmn.engineer (michael meyer)</webMaster>
    <copyright>© 2024 michael meyer</copyright>
    <lastBuildDate>Tue, 31 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://the.hmn.engineer/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>use your words</title>
      <link>https://the.hmn.engineer/posts/use-your-words/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><author>mike@hmn.engineer (michael meyer)</author>
      <guid>https://the.hmn.engineer/posts/use-your-words/</guid>
      <description>&lt;p&gt;this field has a lot of people who got here sideways. i&amp;rsquo;m one of them.&lt;/p&gt;&#xA;&lt;p&gt;i know enough to get around. i can read code, understand what it&amp;rsquo;s doing at face value, catch something that looks wrong. years of working alongside engineers will do that for you, and honestly, it had to: you can&amp;rsquo;t manage a technical team from a position of total bewilderment. but building something from the ground up was always where i&amp;rsquo;d hit a ceiling. i was a GUI guy in a world that occasionally required a terminal.&lt;/p&gt;</description>
    </item>
    <item>
      <title>going with the flow</title>
      <link>https://the.hmn.engineer/posts/going-with-the-flow/</link>
      <pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><author>mike@hmn.engineer (michael meyer)</author>
      <guid>https://the.hmn.engineer/posts/going-with-the-flow/</guid>
      <description>&lt;p&gt;let me set the scene.&lt;/p&gt;&#xA;&lt;p&gt;it was late 2024. our team had just made the decision to move our entire mac fleet from &lt;a href=&#34;https://www.jamf.com&#34;&gt;Jamf Pro&lt;/a&gt; to &lt;a href=&#34;https://fleetdm.com&#34;&gt;Fleet&lt;/a&gt;. renewal was coming up. we didn&amp;rsquo;t want to renew. this was fine.&lt;/p&gt;&#xA;&lt;p&gt;the timeline we gave ourselves: 9 days.&lt;/p&gt;&#xA;&lt;p&gt;the &lt;a href=&#34;https://the.hmn.engineer/posts/fleet-migration/&#34;&gt;migration backstory is here&lt;/a&gt;. what i want to talk about is the engine underneath it: the Okta Workflows system that made the whole thing run itself.&lt;/p&gt;</description>
    </item>
    <item>
      <title>the migration that made us curious again</title>
      <link>https://the.hmn.engineer/posts/fleet-migration/</link>
      <pubDate>Wed, 26 Feb 2025 00:00:00 +0000</pubDate><author>mike@hmn.engineer (michael meyer)</author>
      <guid>https://the.hmn.engineer/posts/fleet-migration/</guid>
      <description>&lt;p&gt;in november 2024, my team migrated macOS device management providers from Jamf Pro to Fleet Device Management. it took 9 days. it went well. and i&amp;rsquo;ve been meaning to write about it ever since.&lt;/p&gt;&#xA;&lt;p&gt;here&amp;rsquo;s the thing about writing a migration story over a year later in my world: the landscape has already shifted. Apple shipped &lt;a href=&#34;https://support.apple.com/guide/apple-business-manager/axm3a49a769d/web&#34;&gt;native MDM migration support&lt;/a&gt; in macOS 26, complete with admin-set deadlines and enforced re-enrollment. Jamf announced a &lt;a href=&#34;https://www.jamf.com/blog/jnuc-2025-keynote/&#34;&gt;unified Platform API ecosystem&lt;/a&gt; at JNUC 2025 that addresses a lot of the API fragmentation we ran into. the world has moved.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
