DEV Community: Anushka Shinde

Why I Chose to Learn Cloud Computing as a Full-Stack Developer

Anushka Shinde — Sat, 09 May 2026 04:18:48 +0000

It Started With Job Descriptions

Every job description I opened had the same words AWS, cloud, scalable infrastructure, cloud-native.

I knew Java. I knew React. I knew databases.But cloud? I kept skipping that part hoping it wouldn't matter.

It clearly wasn't going away.

What Even Is Cloud Computing?

Cloud computing is the delivery of computing services — servers, storage, databases, networking,
software over the internet. Instead of owning your own hardware, you rent what you need, when you need it.

Simple concept.
Massive implications.

Why It Matters for Full-Stack Developers

As a full-stack developer you build applications.But where does that application live after
you build it?

Not on your laptop forever.Not on your college server.In the real world it lives on cloud.

Understanding cloud means understanding:

How your app scales when 1000 users hit it at once
How your data stays secure and backed up
How to deploy without it breaking everything
How much it actually costs to run

These aren't "DevOps problems" anymore.
These are developer problems.

Why I Specifically Chose AWS

AWS has over 200 services.It powers a huge chunk of the internet.And almost every company hiring freshers mentions it.

I started with AWS Cloud Practitioner Essentials ,a free course on AWS Skill Builder.
13 modules. 12+ hours. Completely free.

No prior cloud knowledge needed.
Just curiosity and time.

What Surprised Me

I expected it to be intimidating.
It wasn't.

The concepts made sense once I connected them to things I already knew as a developer.

EC2 is basically a computer you rent.S3 is storage you don't have to manage.RDS is your database but on cloud.

Everything clicked faster than I expected because I already understood what problems these services were solving.

Why You Should Learn It Too

If you're a developer — full stack, backend, frontend, doesn't matter cloud is not optional anymore.

You don't need to become a cloud architect.
You just need to understand enough to:

Deploy your own projects
Talk about it confidently in interviews
Stop skipping those job descriptions

Start free. Start small. Start now.

I Still Have Open Questions — Help Me Out

I'm currently learning cloud and actively looking for ways to actually use it in my projects not just certifications on paper.

A few things I'm genuinely unsure about:

How do developers actually start deploying their own projects on AWS?
Is it realistic to shift focus from development to deployment as a fresher?
Where do you actually begin when theory ends and real implementation starts?

If you've worked with cloud in real projects. I'd genuinely love to hear how you started and what you wish you knew earlier.

And if you've made the shift from development to deployment was it worth it?
Drop your honest experience below 👇

🔗 More about me: dev.to/anushka_shinde_99

The Truth About CS Projects Nobody Talks About

Anushka Shinde — Fri, 08 May 2026 09:04:28 +0000

Every CS student has made a project because they had to.

Not because they wanted to. Not because they had a great idea. Because the syllabus said so and marks depended on it.

And that's completely okay.

But here's what most students miss that forced project? It can be the best thing on your resume. If you let it.

My First Project Made Me Cry

I'm not exaggerating.

My first academic project was a mess. Broken logic, ugly UI, half the features not working. I stayed up nights just trying to make it submit without crashing.

But it came together. Somehow, it always does.

And the next semester? I remembered every mistake. I avoided them. I built something bigger. Something better.

Then the next semester same thing. Bigger. Better. Cleaner code. New features I didn't even know existed last time.

The Pattern I Noticed

Each semester I discovered something new a library, a design pattern, a better way to handle forms, a smarter database structure.

Not because someone taught me.Because I was building something real and
ran into a real problem that needed a real solution.

That's how you actually learn.

The Problem With Most Students

We treat academic projects like assignments.

Minimum features. Minimum effort.
Submit. Get marks. Forget.

But what if you treated every academic project like it was going on your resume?Because it can. It should.

You're already spending weeks on it.You're already losing sleep over it.
Why not make it count twice once for marks, once for your career?

AI Gives Everyone The Same Ideas

Yes, AI helps with project ideas.But AI gives the same ideas to everyone.

The student who builds a "library management system" because AI suggested it looks exactly like the 500 other students who got the same
suggestion.

What makes YOUR project stand out is YOU your creativity, your real-world thinking, your unique twist on a common problem.

Be creative. Be real. Be proactive.AI is a tool, not a replacement for your own thinking.

What I Wish Someone Told Me Earlier

Make your project functional, not just presentable
Add one feature that wasn't asked for
Think about real users, not just your professor
Push it to GitHub even if it's messy
Write about what you built and what you learned

Your academic project is already your portfolio. Stop treating it like homework.

Final Thoughts

You are already under pressure every semester.You are already building something.

The only difference between a student who graduates with a strong portfolio and one who doesn't is intention.

Build with intention.
Every. Single. Semester.

Are you a CS student who turned an academic project into something you're proud of? Share it in the comments I'd love to see what you built 😊

How I Built a Blood Bank Management System from Scratch using PHP & MySQL

Anushka Shinde — Fri, 08 May 2026 06:05:00 +0000

Introduction

As a developer, I always wanted to build something that actually matters. Blood banks are critical, yet most of them still run on manual processes. So I built
LifeFlow, a full-stack Blood Bank Management System that connects donors, hospitals, and admins in one platform.

Here's how I built it, what I learned, and the mistakes I made along the way.

What Does LifeFlow Do?

Donors can register, track their donation history, and download certificates
Hospitals can request blood and track availability in real time
Admins manage everything: inventory, camps, requests, and analytics

Three different roles. One unified system.

Tech Stack

Backend: PHP 8.2, PDO
Frontend: HTML, CSS, JavaScript
Database: MySQL
Analytics: Chart.js
Server: Apache / XAMPP

Key Features I'm Proud Of

1. Role-Based Access Control
Each user type (Admin, Hospital, Donor) sees a completely different portal after login. Built using PHP Sessions with full access control on every page.

2. Secure Database Interaction
Used PDO with parameterized queries throughout no raw SQL,reduced SQL injection risk.

3. Analytics Dashboard
Integrated Chart.js to show live inventory trends
and donation statistics makes the admin panel feel like a real product.

4. PDF Certificate Generation
Donors get a unique certificate after each donation with a unique ID — generated dynamically from PHP.

Biggest Challenge

The PRG (Post/Redirect/Get) pattern. When I first built forms, refreshing the page was resubmitting data causing duplicate entries. Implementing PRG properly across 8 modules took time but completely
fixed it.

What I Learned

How to design a normalized database with real relationships (8 tables)
Modular architecture inspired by MVC concepts, though not strictly implemented
That clean code matters more than clever code
Security is not optional parameterized queries from day one

Final Thoughts

LifeFlow is not perfect, but it's real. It solves a real problem, handles real roles, and taught me
more than any tutorial ever could.

If you're a student wondering whether to build something "useful" or something "impressive" , build something useful. Impressiveness follows.

Thanks for reading! If you have questions about any part of the build, drop them in the comments 😊

📝 Note: The GitHub repo currently has a broken
folder structure due to an upload mistake working on fixing it soon!

🔗 GitHub Repository: View apeFlow on GitHub