<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Independent | Shivam Vashishtha</title><link>https://www.shivamvashishtha.com/tag/independent/</link><atom:link href="https://www.shivamvashishtha.com/tag/independent/index.xml" rel="self" type="application/rss+xml"/><description>Independent</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>Independent</title><link>https://www.shivamvashishtha.com/tag/independent/</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>PIC32 Embedded &amp; Real-Time Systems</title><link>https://www.shivamvashishtha.com/project/pic32-embedded-labs/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/pic32-embedded-labs/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> University of Minnesota · Embedded Systems coursework&lt;br>
&lt;strong>Period:&lt;/strong> 2026 · University coursework&lt;br>
&lt;strong>Focus:&lt;/strong> Embedded Systems&lt;br>
&lt;strong>Tools / methods:&lt;/strong> PIC32MX · MPLAB X · XC32 · Embedded C&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>Microcontroller software must coordinate peripheral state, asynchronous events, and deterministic response under resource constraints.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Worked on PIC32 embedded programming and integration of peripheral interfaces.&lt;/li>
&lt;li>Implemented or analyzed interrupt-driven communication and state-machine-based control exercises.&lt;/li>
&lt;li>Studied task scheduling and timing behavior in a microcontroller environment.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A representative embedded workflow configures device clocks, peripheral registers, interrupt priority, and shared state. UART communication requires attention to framing, buffering, ISR execution time, and interaction with foreground logic. Timer-based scheduling introduces jitter and race-condition considerations.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>A completed laboratory exercise is not equivalent to independently developing a safety-certified real-time controller. Timing and reliability claims require tests on the relevant hardware configuration.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>University coursework and hands-on embedded exercises.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>No restricted course solutions or third-party laboratory materials are provided.&lt;/p></description></item><item><title>Scendro — Financial Analytics Prototype</title><link>https://www.shivamvashishtha.com/project/stockscope/</link><pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/stockscope/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Independent software project&lt;br>
&lt;strong>Period:&lt;/strong> Prototype and iterative development&lt;br>
&lt;strong>Focus:&lt;/strong> Software &amp;amp; AI&lt;br>
&lt;strong>Tools / methods:&lt;/strong> React / TypeScript · FastAPI · Python · market-data analysis&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>A financial research interface benefits from separating data acquisition, transformation, model logic, and display so that analysis assumptions remain understandable.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Worked on a web application architecture for market-data research and visualization.&lt;/li>
&lt;li>Built or iterated on interface and backend workflows, including API-driven analytics.&lt;/li>
&lt;li>Explored portfolio views and experimental machine-learning-assisted analysis.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A general architecture consists of a frontend for input and exploration, backend endpoints for validated requests, data loaders with timestamp-aware normalization, and analytical components separate from presentation. Time-series modeling must prevent look-ahead bias and distinguish research experiments from deployable forecasts.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>Market forecasting is vulnerable to nonstationarity, overfitting, and leakage. Backtesting and prediction demonstrations should include transaction assumptions, appropriate holdout periods, and uncertainty, not only visually compelling charts.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Software prototype and experimental analysis; not a claim of validated alpha, automated trading, or financial advice.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>No private API credentials, proprietary datasets, or unverified return claims are shared.&lt;/p></description></item><item><title>Vivisys — Healthcare Software</title><link>https://www.shivamvashishtha.com/project/vivisys/</link><pubDate>Wed, 01 May 2024 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/vivisys/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Independent / collaborative software&lt;br>
&lt;strong>Period:&lt;/strong> Application prototype&lt;br>
&lt;strong>Focus:&lt;/strong> Web Development&lt;br>
&lt;strong>Tools / methods:&lt;/strong> Frontend web app · UI components · data modeling&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>Healthcare-management interfaces must organize structured information clearly while accounting for data sensitivity and workflow correctness.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Contributed to a web-based healthcare-management application.&lt;/li>
&lt;li>Worked on frontend organization and interface-level workflows.&lt;/li>
&lt;li>Explored connections between user-facing functionality and application data structures.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A maintainable application separates UI components, domain logic, validation, and data access. In healthcare contexts, role separation, auditability, and privacy-by-design are essential engineering considerations, even for prototypes.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>The existence of application source code does not imply clinical validation, production deployment, regulatory compliance, or handling of real patient records.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Collaborative application prototype; no claim of clinical deployment or compliance certification.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>Software project description and public source reference; no personal health records or private application data.&lt;/p></description></item><item><title>Mathular — Mathematics Learning Platform</title><link>https://www.shivamvashishtha.com/project/example/</link><pubDate>Wed, 01 Jun 2022 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/example/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Collaborative software project&lt;br>
&lt;strong>Period:&lt;/strong> Educational web project&lt;br>
&lt;strong>Focus:&lt;/strong> Web Development&lt;br>
&lt;strong>Tools / methods:&lt;/strong> Jekyll · LaTeX · web content&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>Educational resources need accessible explanations, navigable mathematical notation, and consistent organization.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Participated in collaborative development of a mathematics-learning resource.&lt;/li>
&lt;li>Worked with structured web content and the presentation of mathematical material.&lt;/li>
&lt;li>Used web technologies and LaTeX-oriented content workflows.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A static-site approach can separate authored learning content from layout, while supporting revision control and consistent page templates. Mathematical notation requires special attention to legibility and mobile rendering.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>The public source repository belongs to a collaborator; the full application and all contributions should not be attributed to one person.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Educational collaborative software project; individual authorship is not implied for the entire repository.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>Only public project context and its linked source repository are referenced.&lt;/p></description></item></channel></rss>