<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Portfolio on Brian Mehrman</title>
    <link>http://brianmehrman.com/portfolio/</link>
    <description>Recent content in Portfolio on Brian Mehrman</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://brianmehrman.com/portfolio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Diagram Builder</title>
      <link>http://brianmehrman.com/portfolio/diagram-builder/</link>
      <pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate>
      <guid>http://brianmehrman.com/portfolio/diagram-builder/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;
&lt;p&gt;Diagram Builder is an open-source code visualization platform built to make large codebases navigable. It parses repositories into a dependency graph, renders them in both 2D and 3D layouts, and exports to multiple formats.&lt;/p&gt;
&lt;h2 id=&#34;what-it-does&#34;&gt;What It Does&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Repository parsing&lt;/strong&gt; — scans source files and builds a typed dependency graph of modules, classes, and functions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2D and 3D layouts&lt;/strong&gt; — force-directed and radial-BFS algorithms render the graph at different levels of abstraction&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Semantic tiered views&lt;/strong&gt; — zoom from architecture-level down to individual module dependencies&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Export&lt;/strong&gt; — outputs to JSON, SVG, and image formats for documentation and diagramming tools&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;how-it-was-built&#34;&gt;How It Was Built&lt;/h2&gt;
&lt;p&gt;Built using an agent-driven development workflow with Claude Code and the Anthropic SDK. Most of the core graph logic and Three.js rendering pipeline was developed through iterative agent sessions, with human oversight on architecture decisions and API design.&lt;/p&gt;</description>
    </item>
    <item>
      <title>On-Demand Kubernetes Test Environments</title>
      <link>http://brianmehrman.com/portfolio/kubernetes-test-environments/</link>
      <pubDate>Sat, 01 Apr 2023 00:00:00 +0000</pubDate>
      <guid>http://brianmehrman.com/portfolio/kubernetes-test-environments/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;
&lt;p&gt;Basis Technologies ran shared long-lived integration environments. Engineers queued up, stepped on each other&amp;rsquo;s changes, and environment contention was a constant source of delays. Setting up a fresh environment could take days — sometimes weeks if infrastructure issues arose.&lt;/p&gt;
&lt;h2 id=&#34;the-solution&#34;&gt;The Solution&lt;/h2&gt;
&lt;p&gt;I designed and led the build of an on-demand full-stack environment system on AWS EKS. Each environment runs the full platform stack: application services, data warehouse, event streaming, and persistent storage.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Company-Wide CI/CD Pipeline Standard</title>
      <link>http://brianmehrman.com/portfolio/cicd-pipeline-standard/</link>
      <pubDate>Wed, 01 Jun 2022 00:00:00 +0000</pubDate>
      <guid>http://brianmehrman.com/portfolio/cicd-pipeline-standard/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;
&lt;p&gt;Engineering teams at Basis were building and maintaining their own CI/CD pipelines independently. There was no standard. Pipelines varied in quality, lacked consistent artifact management, and created ongoing maintenance burden for each team.&lt;/p&gt;
&lt;h2 id=&#34;the-solution&#34;&gt;The Solution&lt;/h2&gt;
&lt;p&gt;I designed and authored the company-wide CI/CD pipeline standard — a 14-stage pipeline that became the default for all engineering services.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The 14-stage pipeline includes:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Source checkout&lt;/li&gt;
&lt;li&gt;Dependency installation&lt;/li&gt;
&lt;li&gt;Static analysis / linting&lt;/li&gt;
&lt;li&gt;Unit tests&lt;/li&gt;
&lt;li&gt;Integration test trigger&lt;/li&gt;
&lt;li&gt;Docker multi-stage build&lt;/li&gt;
&lt;li&gt;Image tagging (semantic versioning)&lt;/li&gt;
&lt;li&gt;Security scanning&lt;/li&gt;
&lt;li&gt;Artifact registry push&lt;/li&gt;
&lt;li&gt;Staging deploy&lt;/li&gt;
&lt;li&gt;Smoke tests&lt;/li&gt;
&lt;li&gt;Production deploy gate&lt;/li&gt;
&lt;li&gt;Production deploy&lt;/li&gt;
&lt;li&gt;Post-deploy verification&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Three deployment modes:&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
