<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Arun's Portfolio</title><link>https://portfolio.struct.work/tags/automation/</link><description>Recent content in Automation on Arun's Portfolio</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 07 Apr 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://portfolio.struct.work/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>ETABuddy - ETABS Diagnostic Toolkit</title><link>https://portfolio.struct.work/posts/etabuddy-etabs-diagnostic-toolkit/</link><pubDate>Tue, 07 Apr 2026 10:00:00 -0700</pubDate><guid>https://portfolio.struct.work/posts/etabuddy-etabs-diagnostic-toolkit/</guid><description>&lt;p&gt;ETABS is the industry-standard software for structural analysis of buildings, but its warning system is notoriously cryptic. A single model run can produce hundreds of warnings scattered across log files, each requiring cross-referencing PDFs, forum posts, and tribal knowledge to diagnose. I built ETABuddy to collapse that entire workflow into a single command.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="my-role"&gt;My Role&lt;/h2&gt;
&lt;p&gt;Sole developer. Self-initiated project - identified the problem from daily frustration with ETABS warning diagnosis and built the complete solution end-to-end.&lt;/p&gt;</description></item><item><title>AI Design Companion</title><link>https://portfolio.struct.work/posts/ai-design-companion/</link><pubDate>Tue, 17 Feb 2026 10:00:00 -0700</pubDate><guid>https://portfolio.struct.work/posts/ai-design-companion/</guid><description>&lt;p&gt;Design documentation is one of the first things cut when project budgets are tight - but it is also one of the most valuable artifacts for construction support, peer review, and future reference. I built an AI-agent tool that captures the complete design trail automatically as a byproduct of the design process itself, requiring zero additional time from the engineer.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="my-role"&gt;My Role&lt;/h2&gt;
&lt;p&gt;Sole developer. Self-initiated project - identified the documentation gap and built the solution end-to-end.&lt;/p&gt;</description></item><item><title>Code Comparison Tool</title><link>https://portfolio.struct.work/posts/code-comparison-tool/</link><pubDate>Thu, 22 Jan 2026 10:00:00 -0700</pubDate><guid>https://portfolio.struct.work/posts/code-comparison-tool/</guid><description>&lt;p&gt;When a new edition of a building code is published, engineers must understand every change that affects their practice. Traditionally this means reading both editions side by side - a process that takes days for a major code like the NBCC or BCBC. I built a tool that automates this comparison at the individual clause level, with AI-powered summarization that tells you not just what changed, but whether it matters.&lt;/p&gt;</description></item></channel></rss>