<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Engineering | Shivam Vashishtha</title><link>https://www.shivamvashishtha.com/tag/software-engineering/</link><atom:link href="https://www.shivamvashishtha.com/tag/software-engineering/index.xml" rel="self" type="application/rss+xml"/><description>Software Engineering</description><generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.shivamvashishtha.com/media/icon_hu016cb3b331e9522dbd920334fc7fb877_32429_512x512_fill_lanczos_center_3.png</url><title>Software Engineering</title><link>https://www.shivamvashishtha.com/tag/software-engineering/</link></image><item><title>Engineering Portfolio &amp; Deployment Pipeline</title><link>https://www.shivamvashishtha.com/project/personal-portfolio/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/personal-portfolio/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Independent website&lt;br>
&lt;strong>Period:&lt;/strong> 2026 · Published site&lt;br>
&lt;strong>Focus:&lt;/strong> Software Engineering&lt;br>
&lt;strong>Tools / methods:&lt;/strong> Hugo / Wowchemy · SCSS · GitHub · Netlify&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>A technical portfolio must remain readable, maintainable, and safe to update without interrupting an existing deployment.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Customized a Hugo/Wowchemy static site for projects, experience, and research.&lt;/li>
&lt;li>Adopted branch-based Git workflows and Netlify build/deployment processes.&lt;/li>
&lt;li>Iteratively improved responsive presentation and content organization.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>The publishing pipeline separates authoring from production release: local edits → feature branch → Git commit → remote preview → review → production merge. Static generation avoids a bespoke application backend for standard professional content.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>Website deployment and technical documentation work; future features and proposed demonstrations are not treated as implemented.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Deployed personal website with version-controlled content and deployment configuration.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>Only public-facing site code and content are linked.&lt;/p></description></item><item><title>Transmission Engineering Workflow Automation</title><link>https://www.shivamvashishtha.com/project/power-system-automation/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/power-system-automation/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Xcel Energy · Transmission Modeling&lt;br>
&lt;strong>Period:&lt;/strong> 2024–2026 · Engineering software&lt;br>
&lt;strong>Focus:&lt;/strong> Software Engineering&lt;br>
&lt;strong>Tools / methods:&lt;/strong> Python · structured data · model-file workflows&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>Repetitive study preparation can introduce avoidable inconsistencies when engineering files and reference tables are transformed manually.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Developed or supported software tools for consistent engineering-data handling and validation.&lt;/li>
&lt;li>Worked with structured model inputs, batch checks, and case-preparation workflows.&lt;/li>
&lt;li>Applied software techniques to make routine analytical work easier to repeat and review.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A useful engineering workflow makes inputs explicit, validates schema and identifiers, records warnings separately from errors, and produces reviewable change reports. It should support dry-run comparisons rather than silently modifying study inputs.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>Correct formatting is necessary but insufficient: model changes must still reflect physical and procedural intent. Versioning and traceability matter as much as execution speed.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Engineering automation contributions; not an assertion of public product deployment.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>No proprietary script, operational dataset, file mapping, or internal application architecture is shared.&lt;/p></description></item></channel></rss>