How I Accidentally Became a Full-Stack Web Developer (And Survived)

I didn’t wake up one day and decide to become a full-stack web developer.
It happened slowly… like a bug that you ignore until it becomes production-ready.

What started as “Let me just center this div” turned into building hospital systems, ticket booking platforms, and websites that somehow still work at 3 AM.

Advance Medicity: Because Hospitals Also Deserve Good Software

One day, I asked myself a dangerous question:

“What if hospitals didn’t run on Excel sheets and hope?”

That’s how Advance Medicity was born — a Hospital Management System powerful enough to handle patients, doctors, appointments, billing, and my mental breakdown during deployment.

This system:

• Manages patient records like a responsible adult
• Handles appointments without double-booking reality
• Stores data securely so even bugs can’t find it (most of the time)

Doctors were happy. Admins were faster. Servers were… mildly stressed.

Arc Architect: When Pixels Need to Look Expensive

Architects don’t want websites.
They want digital monuments.

So while working on Arc Architect, I carefully placed pixels like concrete blocks. Every animation was smooth. Every layout was precise. Every font was judged silently.

The challenge?
Making the website look premium without making the browser cry.

Mission status: Architecturally Approved™

Bingo Circus: Where Traffic Attacks in Groups

Then came Bingo Circus, a ticket booking system where users arrive together… aggressively.

This project taught me:

• What “scalability” actually means
• Why databases deserve respect
• How fast bugs multiply under pressure

Users booked tickets. Payments worked. Servers survived.
I aged five years in one deployment.

My Superpowers (Unlocked After Too Much Coffee)

I build things using:

• HTML, CSS, JavaScript (the holy trinity)
• Backend logic that only breaks on weekends
• Databases that remember things better than I do
• GitHub commits that say “final-final-fix-v3”

I specialize in turning ideas → code → panic → solutions.

My Development Philosophy

I follow a strict workflow:

1. Build the feature
2. Break the feature
3. Google the error
4. Fix the feature
5. Break something else
6. Call it “experience”

This process has never failed me.
(It has failed the server, though.)