<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>My Projects on Sumukh Acharya</title><link>https://sumukh-acharya.vercel.app/projects/</link><description>Recent content in My Projects on Sumukh Acharya</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://sumukh-acharya.vercel.app/projects/index.xml" rel="self" type="application/rss+xml"/><item><title>Senior Vision AI</title><link>https://sumukh-acharya.vercel.app/projects/senior-vision/</link><pubDate>Fri, 15 Aug 2025 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/senior-vision/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/Senior-Vision-AI" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Scan-n-Say&lt;/strong&gt; is a mobile web app that helps elderly and visually impaired users shop independently at supermarkets. Point your phone camera at any product, and the app reads out a simple, friendly summary of what&amp;rsquo;s on the label — no squinting required.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;Product labels are a nightmare — tiny fonts, dense ingredient lists, unfamiliar terms. For older adults or anyone with low vision, this makes supermarket shopping unnecessarily hard. I wanted to fix that with something genuinely useful: a tool that strips away the noise and just tells you what you need to know.&lt;/p&gt;</description></item><item><title>Grid Pulse</title><link>https://sumukh-acharya.vercel.app/projects/grid-pulse/</link><pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/grid-pulse/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/Grid-Pulse" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Grid-Pulse&lt;/strong&gt; is a real-time data pipeline that turns F1 race weekends into a live stock market. Every driver has a stock value that rises and falls based on their performance — qualifying laps, race positions, practice results — visualised on a live dashboard that updates as events unfold.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;F1 is already obsessive about data. I wanted to explore what it would look like to model driver performance as a financial instrument — and use it as a real excuse to build a proper streaming data pipeline from scratch, not just a toy script.&lt;/p&gt;</description></item><item><title>URL Shortener</title><link>https://sumukh-acharya.vercel.app/projects/url-shortener/</link><pubDate>Sat, 15 Mar 2025 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/url-shortener/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/URL-Shortener" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;A production-grade URL shortening service — the kind of system you&amp;rsquo;d actually deploy, not just demo. Built with Flask and Redis, containerised with Docker, and orchestrated on Kubernetes with autoscaling, load balancing, and health monitoring out of the box.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;URL shorteners are a classic system design problem. I wanted to go beyond the basic implementation and actually build it the way it would run in production — with horizontal scaling, ingress routing, and the ability to handle real traffic spikes without falling over.&lt;/p&gt;</description></item><item><title>DFOS</title><link>https://sumukh-acharya.vercel.app/projects/dfos/</link><pubDate>Fri, 15 Nov 2024 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/dfos/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/DFOS" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;A multi-client file transfer system built from scratch in Python — no frameworks, just raw sockets. Clients authenticate, get their own isolated storage directory on the server, and can upload, download, preview, or delete files concurrently without stepping on each other.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;I wanted to understand what actually happens under the hood when files move across a network — before abstractions like FTP clients or cloud SDKs hide all the interesting parts. Building it at the socket level made the concurrency and protocol design problems impossible to ignore.&lt;/p&gt;</description></item><item><title>Dynamic Fare Engine</title><link>https://sumukh-acharya.vercel.app/projects/dynamic-fare/</link><pubDate>Thu, 10 Oct 2024 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/dynamic-fare/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/Dynamic-Fare-Engine" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;A fare forecasting system for RideWave, a fictional urban mobility company operating bikes, autos, and cars in Quahog City. Given three years of hourly fare data (2021–2023), I built predictive models for each vehicle type and combined them into an ensemble to power dynamic pricing recommendations.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;Dynamic pricing is one of the more interesting applied ML problems — it sits at the intersection of time series forecasting, business strategy, and real operational constraints. I wanted to work through the full pipeline: exploratory analysis, model selection, feature engineering, and ensemble design, rather than just fitting a single off-the-shelf model.&lt;/p&gt;</description></item><item><title>Streamly</title><link>https://sumukh-acharya.vercel.app/projects/streamly/</link><pubDate>Tue, 10 Sep 2024 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/streamly/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/Streamly" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;A data analysis and modelling project for Streamly, a fictional streaming platform. Using their catalogue and engagement data, I analysed what content actually drives user retention and built regression models to predict it — giving the business a data-backed foundation for content decisions.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;Streaming platforms live and die by retention. I was curious about what the data actually says when you cut through intuition — does budget correlate with ROI? Do certain genres retain users better than others? This project was about asking those questions rigorously and letting the analysis answer them.&lt;/p&gt;</description></item><item><title>Restaurant Ordering System</title><link>https://sumukh-acharya.vercel.app/projects/restaurant/</link><pubDate>Mon, 15 Apr 2024 00:00:00 +0000</pubDate><guid>https://sumukh-acharya.vercel.app/projects/restaurant/</guid><description>&lt;p&gt;&lt;a href="https://github.com/sumukhacharya03/Restaurant-Ordering-System" target="_blank" rel="noopener noreferrer"&gt;
 GitHub →
&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="what-is-it"&gt;What is it?&lt;/h3&gt;
&lt;p&gt;A client-server restaurant ordering system built in Python using raw sockets, secured with SSL/TLS. Clients can browse the menu, place orders, and get a GST-calculated bill — all over an encrypted connection.&lt;/p&gt;
&lt;h3 id="why-i-built-it"&gt;Why I built it&lt;/h3&gt;
&lt;p&gt;This was an early deep-dive into network programming. I wanted to understand how client-server communication actually works at the socket level, and adding SSL on top made it a practical exercise in securing that channel — not just making things talk, but making them talk safely.&lt;/p&gt;</description></item></channel></rss>