<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Michael Morrison</title><link>https://michaelmorrison.com/tags/software/</link><description>Recent content in Software on Michael Morrison</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jun 2026 00:00:00 -0700</lastBuildDate><atom:link href="https://michaelmorrison.com/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Standing on Surfaces That Move</title><link>https://michaelmorrison.com/essays/standing-on-surfaces-that-move/</link><pubDate>Mon, 08 Jun 2026 00:00:00 -0700</pubDate><guid>https://michaelmorrison.com/essays/standing-on-surfaces-that-move/</guid><description>&lt;p&gt;The software engineering job has moved, seemingly overnight. Working engineers have not been deleted wholesale; the disappearance loudly predicted in recent years simply hasn&amp;rsquo;t happened. The work itself has moved, though, and the move is measurable. Line-by-line typing of code got cheap. The judgment about what&amp;rsquo;s worth typing, and whether what&amp;rsquo;s been typed will hold together at scale, got expensive. In fact the latter was always expensive, but the cheapening of coding itself has made the gap between the two meaningful.&lt;/p&gt;</description></item></channel></rss>