<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Building on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/building/</link><description>Recent content in Building on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/building/index.xml" rel="self" type="application/rss+xml"/><item><title>The side project mirror</title><link>https://blog.vnykmshr.com/writing/the-side-project-mirror/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/the-side-project-mirror/</guid><description>&lt;p&gt;The job title says architect. The side project says &amp;ldquo;why is this Dockerfile 300MB, let me fix this real quick&amp;rdquo; &amp;ndash; three hours later, still shaving layers, completely happy.&lt;/p&gt;
&lt;p&gt;Nobody assigns you ops on a side project. Nobody assigns you anything. But there you are, writing monitoring for something with twelve users, eleven of them are you in different browsers.&lt;/p&gt;
&lt;p&gt;The role is what someone else decided you were good at. The side project is what your hands reach for when nobody&amp;rsquo;s directing them. Sometimes they match. Mostly they don&amp;rsquo;t. The backend engineer with strong opinions about font spacing. The tech lead who&amp;rsquo;d rather be tailing logs than running standups. The platform architect who writes a blog engine from scratch and tells you with a straight face that the existing ones were fine, just not the way they&amp;rsquo;d do it.&lt;/p&gt;</description></item></channel></rss>