<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Paper Weight</title>
    <link>https://matthew-mccabe.com/</link>
    <description>Recent content on Paper Weight</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>@ 2026 JSON Alexander</copyright>
    <lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://matthew-mccabe.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Game Dev Case Study: Visual Language in Directed Exploration</title>
      <link>https://matthew-mccabe.com/post/outlast2-case-study/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/post/outlast2-case-study/</guid>
      <description>&lt;h2 id=&#34;outlast-2-visual-language-in-directed-exploration&#34;&gt;Outlast 2: Visual Language in Directed Exploration&lt;/h2&gt;&#xA;&lt;h3 id=&#34;warning-contains-a-gameplay-image-of-a-mutilated-cow&#34;&gt;[WARNING] Contains a gameplay image of a mutilated cow&lt;/h3&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;I just had some ideas on visual language in horror game dev and they led me to analyze a section of Outlast 2, but first here is the thought I had:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;div align=&#34;center&#34;&gt;&#xD;&#xA;&lt;p&gt;In my game, the house is a playable area and it&amp;rsquo;s both pretty and useful narratively inside, while being a necessary component of the viewport from the outside – but not the focal point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Raw Indignation</title>
      <link>https://matthew-mccabe.com/post/revisions-indignation/</link>
      <pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/post/revisions-indignation/</guid>
      <description>&lt;p&gt;Texans stomped steelers, I refuse to build things on windows through GUIs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>https://matthew-mccabe.com/about/</link>
      <pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/about/</guid>
      <description>&lt;p&gt;Paper Weight is my technical notebook and build log.&lt;/p&gt;&#xA;&lt;p&gt;I use it to document things I build, break, debug, deploy, and eventually understand well enough to explain. Most posts live somewhere between engineering notes, project logs, infrastructure experiments, and occasional rants.&lt;/p&gt;&#xA;&lt;p&gt;The main subjects are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;cloud infrastructure&lt;/li&gt;&#xA;&lt;li&gt;Linux tooling&lt;/li&gt;&#xA;&lt;li&gt;static sites&lt;/li&gt;&#xA;&lt;li&gt;backend and systems work&lt;/li&gt;&#xA;&lt;li&gt;game development&lt;/li&gt;&#xA;&lt;li&gt;personal software projects&lt;/li&gt;&#xA;&lt;li&gt;debugging stories&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The goal is not to write polished tutorials for strangers. The goal is to keep a public record of implementation details, tradeoffs, mistakes, fixes, and ideas I would otherwise forget.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://matthew-mccabe.com/contact/</link>
      <pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/contact/</guid>
      <description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/mccabematthew&#34;&gt;GitHub&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://ec2-18-116-70-40.us-east-2.compute.amazonaws.com/hw14/portfolio.html&#34;&gt;Portfolio&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Hugo: A Solutions-First Web Stack</title>
      <link>https://matthew-mccabe.com/post/hugo-hell/</link>
      <pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/post/hugo-hell/</guid>
      <description>&lt;hr&gt;&#xA;&lt;p&gt;I spent the last week rebuilding parts of my site stack and figuring out what I actually want my workflow to look like going into the next few months.&lt;/p&gt;&#xA;&lt;p&gt;Turns out the answer is probably:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;static sites&lt;/li&gt;&#xA;&lt;li&gt;Go binaries&lt;/li&gt;&#xA;&lt;li&gt;cheap infrastructure&lt;/li&gt;&#xA;&lt;li&gt;terminal-first tooling&lt;/li&gt;&#xA;&lt;li&gt;and significantly less JavaScript than the modern internet would like me to use ( but not no javascript ;) )&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;getting-going&#34;&gt;Getting Going&lt;/h2&gt;&#xA;&lt;p&gt;Hugo felt opaque when I first fiddled around with a theme.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>https://matthew-mccabe.com/archives/</link>
      <pubDate>Tue, 28 May 2019 00:00:00 +0000</pubDate>
      <guid>https://matthew-mccabe.com/archives/</guid>
      <description></description>
    </item>
  </channel>
</rss>
