<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Colin Milhaupt</title>
    <link>http://localhost:1313/</link>
    <description>Recent content on Colin Milhaupt</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 01 Jun 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Navigating LLMs as Developers: A Framework for Responsible Use</title>
      <link>http://localhost:1313/posts/responsible-llm-use/</link>
      <pubDate>Sun, 01 Jun 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/responsible-llm-use/</guid>
      <description>Large Language Models have been positioned as powerful tools for developers. And they are nothing more than tools. But like any tool in our arsenal, they come with their own set of risks that need to be understood and managed carefully.&#xA;The Double-Edged Sword The risks posed by LLMs to developers are real and worth examining. First, there&amp;rsquo;s the risk of cheating ourselves out of thought. When we lean too heavily on these models, we might be bypassing the critical thinking process that makes us better engineers.</description>
    </item>
    <item>
      <title>More WiFi without internet on a Southwest flight</title>
      <link>http://localhost:1313/posts/more-southwest/</link>
      <pubDate>Wed, 04 Oct 2023 11:24:00 -0600</pubDate>
      <guid>http://localhost:1313/posts/more-southwest/</guid>
      <description>After reading James Vaughan&amp;rsquo;s write-up about what he could do with a connection to the flight’s WiFi without access to the internet, and an upcoming Southwest flight of my own, I&amp;rsquo;d thought I&amp;rsquo;d replicate his findings and see what else was lurking around the airlines&amp;rsquo; network.&#xA;First, the data collection:&#xA;while true; do http getconnected.southwestwifi.com/current.json | jq &amp;gt; current_$(date +%Y%m%d%H%M).json; sleep 60; done I started this maybe 30 minutes into my flight so wasn&amp;rsquo;t able to get the full duration, but at the end the data checks out!</description>
    </item>
  </channel>
</rss>
