<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web Development | Shivam Vashishtha</title><link>https://www.shivamvashishtha.com/tag/web-development/</link><atom:link href="https://www.shivamvashishtha.com/tag/web-development/index.xml" rel="self" type="application/rss+xml"/><description>Web Development</description><generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><lastBuildDate>Wed, 01 May 2024 00:00:00 +0000</lastBuildDate><image><url>https://www.shivamvashishtha.com/media/icon_hu016cb3b331e9522dbd920334fc7fb877_32429_512x512_fill_lanczos_center_3.png</url><title>Web Development</title><link>https://www.shivamvashishtha.com/tag/web-development/</link></image><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>