

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://some-natalie.dev/</id>
  <title>Some Natalie's corner of the internet</title>
  <subtitle>Things I'm learning, working on, or thinking about.  All opinions and snark my own.</subtitle>
  <updated>2026-10-08T12:49:59-04:00</updated>
  <author>
    <name>Natalie Somersall</name>
    <uri>https://some-natalie.dev/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://some-natalie.dev/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://some-natalie.dev/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Natalie Somersall </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Four years of writing on the internet</title>
    <link href="https://some-natalie.dev/blog/four-years/" rel="alternate" type="text/html" title="Four years of writing on the internet" />
    <published>2026-10-02T00:00:00-04:00</published>
  
    <updated>2026-10-02T17:09:21-04:00</updated>
  
    <id>https://some-natalie.dev/blog/four-years/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/four-years/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>A few observations and thoughts about writing on the internet for four years.  Doing fewer, bigger things  📝  This is post #130, meaning only 20 pieces this year.  It’s much less than prior years, down from 32 and 42 posts per year the past two.  This was my busiest year so far, for better and worse.  Writing less seems like a reasonable trade for all the learning.  🎤 It was a thrill to speak a...</summary>

  </entry>

  
  <entry>
    <title>Reviewing slop and asking for better feedback</title>
    <link href="https://some-natalie.dev/blog/slop-reviews/" rel="alternate" type="text/html" title="Reviewing slop and asking for better feedback" />
    <published>2026-09-28T00:00:00-04:00</published>
  
    <updated>2026-09-28T00:00:00-04:00</updated>
  
    <id>https://some-natalie.dev/blog/slop-reviews/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/slop-reviews/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>My AI slop annoys me.  Your AI slop annoys me, but probably not as much as my own slop annoys me.  We shouldn’t review it more than we have to, yet here we are. 🙄  We need to work together anyways.     Let’s talk about how to ask for feedback on your AI slop without ruining your relationships.  No judgement … well, not much judgement anyways.   Economics 101  A teammate I’ll call Bob asked me t...</summary>

  </entry>

  
  <entry>
    <title>Bumping vendored dependencies in a repository</title>
    <link href="https://some-natalie.dev/blog/bump-vendored-deps/" rel="alternate" type="text/html" title="Bumping vendored dependencies in a repository" />
    <published>2026-09-15T00:00:00-04:00</published>
  
    <updated>2026-10-08T12:49:07-04:00</updated>
  
    <id>https://some-natalie.dev/blog/bump-vendored-deps/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/bump-vendored-deps/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>I have a love/hate relationship with vendoring dependencies in a repository.  This enduring trauma and admiration comes from many of the projects I’ve supported over the years.  Vendoring is a terribly convenient pattern, doubly so when the upstream source of that dependency could be unavailable when/where you’re running that project.  Corporate firewalls or proxies, unstable connectivity on cu...</summary>

  </entry>

  
  <entry>
    <title>Bumping dependencies inside Dockerfiles</title>
    <link href="https://some-natalie.dev/blog/bump-deps-in-dockerfiles/" rel="alternate" type="text/html" title="Bumping dependencies inside Dockerfiles" />
    <published>2026-09-08T00:00:00-04:00</published>
  
    <updated>2026-10-08T12:49:07-04:00</updated>
  
    <id>https://some-natalie.dev/blog/bump-deps-in-dockerfiles/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/bump-deps-in-dockerfiles/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>There are a ton of weird, non-standard places to manage dependencies that don’t work with software composition tools or package managers.  Somehow I seem to find many of these reasons.  Each made sense at the time and for the project … but had a hidden cost.  Departing from the “paved path” of a package manager means updating and maintaining that dependency becomes a manual process.  The tools,...</summary>

  </entry>

  
  <entry>
    <title>Building a yum repo in GitHub Pages</title>
    <link href="https://some-natalie.dev/blog/yum-repo-github-pages/" rel="alternate" type="text/html" title="Building a yum repo in GitHub Pages" />
    <published>2026-09-01T00:00:00-04:00</published>
  
    <updated>2026-09-01T00:00:00-04:00</updated>
  
    <id>https://some-natalie.dev/blog/yum-repo-github-pages/</id>
    <content type="text/html" src="https://some-natalie.dev/blog/yum-repo-github-pages/" />
    <author>
      <name>Natalie Somersall</name>
    </author>

  
    
  

  <summary>But why though?  I’ve been running a kernel build with a patch to enable addressing of identical hardware individually for around 8 years.  Until now, users would have to either build it themselves with those directions or go to the GitHub repo and download a zip file to install the packages manually.  Neither are easy or friendly to use.  Building the Linux kernel for dedicated hardware VMs ou...</summary>

  </entry>

</feed>


