Year One - No Projects, No Pressure
My first year was comfortable. Just learning programming languages.
No projects. No pressure.
I had no idea what was coming.
Year Two Hit Differently
Suddenly - projects.
Announced just two to three months before submission.
No real guidance on how to build one.No idea where to start.
ChatGPT existed but wasn't reliable yet.The responses were basic. Full of errors.More confusing than helpful sometimes.
So I did what made sense at that moment , I copied.
Not someone's actual code.
But the idea. The structure. The flow.I mimicked real projects. Made dummy versions.Watched YouTube tutorials and rebuilt
what I saw.
That was my starting point.And I'm not ashamed of it.Everyone starts somewhere.
The Course That Changed Everything
My college provided a free Full Stack Java Development course.
That's where I first touched:
- Core Java and Advanced Java
- Spring Boot
- Angular
- Hibernate
- MySQL
But here's the problem everything was taught individually.
Spring Boot alone.Angular alone.
MySQL alone.
Nobody showed us how they connect.Nobody showed us how to build an actual application using all of them together.
We had to figure that out ourselves.
Building My First Real Project — E-Medical System
Our team decided to build an E-Medical Management System.
But before writing a single line of code we went outside.
Literally.
We visited medical shops in our hometown.Small ones. Big ones.
We talked to shop owners about what kind of system they actually needed.
What we found was interesting:
- Small shops had no system at all , everything was manual
- Bigger shops had systems so complicated that only young, tech-savvy people could use them
- Middle-aged shop owners were completely lost with complex interfaces
So we gathered real requirements from a real small shop owner.
Built something that actually solved a real problem.
That research changed how I think
about projects forever.
How We Actually Built It
We had learned Angular and Spring Boot individually with no idea how they connected in a real application.
So here's what we did:
- Designed every page on paper first
- Built the frontend in Angular with help from ChatGPT
- Gave that frontend code to ChatGPT and asked it to generate matching Spring Boot APIs
- Connected both
- Used Postman to test if APIs were working correctly
- Database was designed around only the data we actually needed nothing extra
It was messy. It was frustrating.
But it worked.And we built it ourselves even if AI helped us connect the dots.
Project After Project Getting Better
After E-Medical I kept building.
A Quiz App.
A Restaurant Management System.
More full stack projects each one
better than the last.
Each project taught me something the previous one didn't.
Each mistake made the next project cleaner.Each frustration made me a better debugger.
And then came LifeFlow
my Blood Bank Management System.
Built completely solo. In PHP and MySQL.The project I'm most proud of.
If you want to read about that one I've already written about it here on DEV.to 😊
Where I Am Now
I'm not just building projects anymore.
I'm learning cloud
AWS, Azure, Google Cloud.
Understanding how applications don't just run on laptops but scale in the real world.
The journey went from:
Copying projects → Mimicking tutorials → Building with AI help → Building solo →Now learning how to deploy and scale.
What I Want You To Take From This
If you're a CS student right now
feeling lost about projects
Start by copying. That's okay.
Then start mimicking. That's progress.Then start adding your own ideas. That's growth.Then go talk to real people about real problems. That's when it gets serious.
You don't need to know everything
before you start.
You just need to start.
The rest figures itself out one frustrating, confusing,
surprisingly satisfying project at a time. 😊
Where are you in your project journey
right now?
Just starting? Already building?
Somewhere in between?
Drop it in the comments —
I'd love to know 👇