Fullstack developer

A small-shop owner needs a quick way to record stock, sales, customer credit, and ask questions about the business without navigating a complex system.

Built the prototype end to end as a personal project while learning agentic AI, tool calling, and MCPs.

Used Python, Gemini tool calls, PostgreSQL, and Telegram.

Replaced several overlapping analytics tools with a flexible query tool, then refined tool descriptions and context to improve tool selection.

The agent could answer a wider range of questions and cover more edge cases.

It remains a prototype and has not been used in a real shop.

Learned to make tools reusable and give the agent clear context instead of creating a separate tool for every question.

A clothing shop needed billing, barcode generation, and inventory management for roughly 2,000 garment items.

Built and customized the UI, application, backend, and database solo; the shop supplied its workflow requirements.

Clarified the underlying shop needs through back-and-forth, then connected barcode scanning, barcode printing, and receipt printing.

Added discount offers, GST, and sales reporting.

The system saved the shop hours of work, made barcode creation and billing more efficient, and helped staff use dashboard data to optimize stock.

I did not bring a stopwatch to checkout, so there is no precise time-saving figure.

Would spend more time understanding the requirements up front to reduce rework and shape a simpler solution.

Validate and normalize HR employee CSVs, catch identity and manager-reference errors, and inspect reporting hierarchies before import.

Implemented the parser, validation, hierarchy analysis, CLI, and Django preview solo.

Used duplicate counters and ID/email lookup maps instead of repeatedly scanning employee rows; used visited-path tracking to find cycle members.

The repository describes O(n) time and O(n) additional memory.

Simulated tests with roughly 10,000–20,000 rows worked well.

The test employees survived; a production HR department has yet to join the party.

Learned to choose data structures and passes that keep large-file validation efficient while preserving clear row-level errors.

Meetup attendees sitting far from the screen struggled to follow slides and revisit the deck after a talk.

Owned the idea, UI, and implementation solo; presenters can share a deck while attendees follow slides, annotate, and download their copy.

Implemented live slide updates with Server-Sent Events.

The key challenge was mirroring presenter actions to all viewers immediately; the current project has not been field-tested.

Still waiting for its first real meetup.

The slides are ready; the audience has yet to RSVP.

Would improve the way presenter actions are mirrored to viewers, then test it at an event.

Preparing next month’s bilingual devotionals manually took two to three hours and was difficult while travelling.

Built the uploader and publishing pipeline solo in about three hours over a weekend.

Parses Tamil and English Word documents into day-wise content, normalizes formatting with code, preprocesses scripture references, generates speech, stores audio in Convex file storage, and publishes article records to Convex DB.

ChatGPT review is a separate manual step.

Turned a multi-hour publishing task into a few clicks that take around ten minutes.

The project renewed an interest in Python and automation, and reinforced matching complexity to the actual need.

Needed a convenient way to collaborate on setup notes without leaving temporary shared content stored permanently.

Built the application end to end solo and tried it personally and with a small group.

Used Socket.IO rooms with temporary in-memory server storage and an owner-controlled edit code.

Room access and editing permissions were the main challenge.

This version is server-relayed, not peer-to-peer or end-to-end encrypted.

Two or three people said it was easy enough to use.

No standing ovation, no angry emails.

For a shared notes tool, I’ll take that.

Would explore peer-to-peer communication and encryption in a future version; neither is implemented in the current project.

Wanted a quick way to shorten a URL without visiting a separate URL-shortening site, while learning Go.

Built the Go service and browser flow solo as a weekend learning project; the builder is its primary user.

Used Go, Gin, and Redis.

A small browser page reads the full URL because browsers do not send the fragment after `#` to the server, then requests a short link and copies it.

Used extensively across my personal links and projects.

The URLs got shorter; the analytics report is still a bit too short.

Learned how browser URL fragments affect server requests and would keep the overall approach.

Daily devotional messages and images in WhatsApp were hard to search, read on a phone, and use to catch up on missed days.

Built the reader, audio workflow, publishing automation, and usage tracking solo.

Created a bilingual Tamil and English daily reader.

Current repositories store devotional text in Convex DB and audio files in Convex file storage; the reader resolves audio URLs for playback.

Simplified an initially overbuilt audio approach.

Reported more than 200 daily active users.

Readers said it was easier to read, listen, catch up, and share a direct link.

Write requirements first and choose an architecture that fits them to avoid overengineering and unnecessary tool changes.

A friend running a Thirukkural Instagram page needed help preparing regular posts after running short on time.

Built the poster generator and API solo; the friend uses its output for Instagram posts.

Compared Thirukkural sources for useful Tamil and English explanations, used Canvas for posters, and Gemini for captions.

The generated posters and captions are used in the friend’s Instagram posts.

The future goal is to automate the whole flow from Kural selection and poster creation through Instagram publishing.

Attendees needed one place for a three-day Coimbatore convention’s schedule, venue guidance, travel preparation, and code of conduct.

Organizers supplied content and media; owned the visual design, frontend development, and deployment.

Built in one day.

Kept the implementation straightforward, then added sermon presentations, audio, and a photo gallery after the event.

Attendees used the site instead of repeatedly asking organizers for details, which made coordination easier.

Would take the same straightforward approach again.

A church youth event needed an engaging site for students, with the agenda and event resources in one place.

Church team supplied the agenda; owned design, development, and deployment.

Used landing-page inspiration to create a minimal blue, white, and black visual theme, with animation, sermon video, presentations, and mobile song sheets.

Attendees could read song sheets on their phones, and another church forked the repo for its own event.

Would keep the same approach because the site worked well for its audience.

Inspired by a friend’s idea, built a small way to package a short personal message and prompt in a shareable link.

Created the browser-only experience.

The browser does the heavy lifting; the hug takes the credit.

Kept the content in the URL rather than adding an app backend.

Long URLs later motivated the separate Into Short URL project.

A hug in a link.

What did you expect, a quarterly earnings report?

No audience numbers to share yet.

The hug was small.

The URL was not.

That little plot twist led to Into Short URL.

Wanted hands-on practice with Go, networking, and SSH, inspired by terminal-based websites and a possible terminal-style portfolio.

Built the prototype solo.

Created a minimal interactive SSH server.

The current repository is a learning prototype, not a full portfolio shell.

The main outcome was learning.

No public usage numbers; the terminal and I had a productive conversation.

Would keep it as a learning project and build on the Go and networking experience.

Needed convenient filler text for automation workflows, available from a browser or terminal.

Built the Go service end to end solo as a learning project.

Used URL paths to request different kinds and amounts of placeholder content, returning plain text or Markdown without a full frontend.

Used in my automation workflow.

No usage stats to share; even the analytics are placeholder text.

Would improve the placeholder content presentation with a more polished style.

Wanted to check live Tamil Nadu election results directly from the terminal.

Owned requirements and implementation end to end.

Built a terminal dashboard that polls election results JSON and redraws seat tallies, candidates, winners, and alliance totals.

Worked as intended, and people who saw it liked the terminal interface.

No broader usage numbers; the terminal had its little fan club.

Would refine the TUI appearance with more color.

Needed voice input for Codex CLI on Linux before a Linux desktop voice option was available.

Built the VS Code extension and local transcription bridge solo.

Captured microphone audio, transcribed it locally, and inserted the result into the active integrated terminal.

Getting text into the correct terminal input and providing a clear recording indicator were key details.

Worked for the builder’s command-line workflow and was used until a desktop app became available.

Kept the extension focused on solving the voice-to-text need rather than adding unrelated features.

As a first-year college student learning Python, wanted to automate joining scheduled online classes and sending the right greeting.

Built as an early Python automation project.

The most demanding teammate was the class timetable.

Moved from screen coordinates and simulated mouse actions to Selenium locators such as element IDs and class names, avoiding dependence on window size.

Used it for about a month, and friends tried the browser-based flow too.

No usage dashboard; this was homework avoidance with extra homework.

Learned that selecting page elements is more robust than automating by fixed screen positions.

A playful browser game made for fun when the builder and friends were bored.

Built as a personal project for a bit of fun.

The punching is virtual; please spare your screen.

A single-page HTML/CSS/JavaScript game uses nine face sprites, health states, impact effects, touch and mouse input, and reset.

It does not implement vibration or image upload.

No audience stats to share.

The pixels have declined to comment on the punching.

Letting players upload an image as the target is a future idea, not an implemented feature.