Skip to content

Software built around the way you work.

Websites, admin panels and office tools your own staff can run.

Tell me what's slowing your team down. I'll build the fix, from the database to the screens, and hand it over with what you need to keep it running. My college's website at jcbmc.ac.in is one example: its office staff update every page themselves.

Hiring? I'm also open to full-time developer roles. View my resume

CurrentlyMaintaining the college website, now live at jcbmc.ac.in

Portrait of Adithya M D
Adithya M DSoftware DeveloperAvailable for workKarnataka, India
What I build
Websites, admin panels, and software for one specific job
Who it's for
Colleges, offices and small businesses
What you get
Working software, documentation and backups, handed over
In use today
2
Live online, or handed over to the staff they were built for and running today.
Built solo, start to finish
2
Every layer built by me. The other 3 were team projects (2 to 6 people); each case study says which parts were mine.
Platforms covered
3
Web, mobile and desktop.

How I can help

Tell me the problem. Here's what I can build.

Each of the first five is backed by a project you can read in full. If your need sits somewhere in between, describe it in your own words and we'll work out together whether it's a good fit.

Selected work

Problems I've already solved

Every project here started with someone who needed something to work better. Each case study shows what was wrong, what I built, the decisions behind it, and where it stands now.

College ERP: web and mobile

Sri JCBM College ERP

Attendance, IA marks and timetables in one system instead of paper and spreadsheets, with the right view for administrators, HODs, faculty and students, on the web and in a mobile app.

  • Java 21
  • Spring Boot
  • Spring Data JPA
  • PostgreSQL
  • Flyway
  • JWT
When
April 2026 – August 2026
Role
Sole developer
Status
Status: Completed

More projects

All projects

Working together

What working with me looks like

Four steps, scaled to the size of the job. A small website moves through them quickly; a larger system gets more checkpoints. Either way, you always know what is being built and why. Each step links to a project where it happened.
  1. We talk it through

    You tell me what's going wrong, who will use the result, and what a good outcome looks like, in your own words. A rough idea is a fine place to start.

    The college website was built around what office staff update themselves: every page, documents and notices.

  2. You approve a plan

    I suggest an approach that fits your budget and the way you work, explain the trade-offs in plain language, and we agree on scope before I write much code.

    The quotation tool became a desktop app because the data is internal and the office already uses Windows PCs.

  3. You see it early

    The work arrives in small pieces you can try as it's built, so feedback shapes it while changes are still cheap. No big reveal at the end.

    The college site ran first as a public preview, then moved to its own server as the admin panel grew.

  4. Your team takes over

    You get the software running, with documentation, backups and admin screens your staff can use without calling me.

    The inventory system shipped with a Windows installer and was handed over to college staff, who use it.

About

Hi, I'm Adithya. I start with the problem, then write the code.

I'm a full-stack developer in Karnataka. Everything I've built so far started with someone who needed it: my college's website and admin panel, its ERP, and desktop tools for its day-to-day administration.

What I care about most is what happens after launch. Can your staff use it without calling me? Is the data safe? Can it grow when your needs do? I build with those answers in mind from the first conversation.

What you can count on

  • Admin screens that people without a technical background can use
  • Paper and spreadsheet work turned into software that does it for you
  • Pages that work as well on a phone as on a desktop
  • Backups you can restore, so your data is never in one place
  • A clean handover: installer, documentation and a working system

Journey

  1. Jul 2026 – nowProject

    Sri JCBM College website

    New public website and admin panel for my college, live at jcbmc.ac.in on the college's own server.

  2. Apr – Aug 2026Project

    Sri JCBM College ERP

    Attendance, IA marks and timetables for every role, on the web and in a mobile app. Built solo from my internship project.

  3. Apr – Jul 2026Project

    Student Tracking System

    Placement records desktop app, built in a team of two.

  4. Feb – Apr 2026Work

    Java Full Stack Internship

    Run by the college's BCA department with experts from MTD, Mysuru. React, Spring Boot and MySQL. My internship project, a College Management Portal, became the starting point for the college ERP.

  5. Oct 2025 – Apr 2026Project

    Vendor Quotation Comparison System

    Desktop tool for comparing vendor quotations and issuing purchase orders. Main developer in a team of six.

  6. 2024Project

    Inventory Management System

    My first project: a C# desktop inventory system for the college. Rewritten in Python by a team of six in 2026, and now in use by college staff.

  7. 2023 – 2026Education

    Bachelor of Computer Applications

    Sri JCBM College, Sringeri.

Got something that needs building?

Tell me what's slowing your team down. I'll tell you honestly what it would take, and whether I'm the right person for it.

adithyamdgowda@gmail.com

Hiring a developer? I'm also open to full-time roles. View my resume.