From Student to Real Projects: What I’m Learning Building Angular + Laravel Apps

Why I’m Writing This

I’m a Computer Science student and a Junior Full Stack Developer, and I decided to start writing on dev.to to document what I’m learning while building real-world applications.

Not tutorials copied from docs.
Not perfect solutions.
Just real problems, mistakes, fixes, and lessons learned.

If you’re studying computer science, starting your dev career, or juggling university with real projects — this is for you.

My Current Stack

Right now, most of my time is spent working with:

• Angular (standalone components, signals, guards, interceptors)

• Laravel (REST APIs, authentication, roles & permissions)

• Docker (local environments, multi-service setups)

• MySQL

• Git

I usually work on projects where frontend and backend actually talk to each other, and that’s where things get interesting (and painful).

What Real Projects Taught Me (So Far)

1. Tutorials Don’t Prepare You for Integration Issues

The hardest problems rarely live in Angular or Laravel alone.

They live in between:

• auth flows breaking between frontend & backend
• mismatched validation rules
• error handling that works... until it doesn't
• CORS, tokens, headers, permissions

That's where most of my learning happens.

2. Security Is Not "Later"

I used to think:

"I'll focus on features first, security later."

Bad idea.

Working on APIs taught me how easy it is to:

• Expose too much data
• Misconfigure auth
• Trust the frontend too much

Now security is part of the design, not a patch

3. Being a Student Can Be a Strength

Studying computer science while coding professionally gives you:

• deeper understanding of fundamentals
• better debugging skills
• more curiosity about why things work

I’m learning to connect:

• university concepts

• real production code

• practical trade-offs

That connection is powerful.

What I’ll Be Writing About Here

On this blog I’ll share:

• Angular & Laravel lessons from real projects
• API design & security mistakes (and fixes)
• Docker & dev workflows that save time
• Computer science concepts explained like a student would want them explained

No guru vibes. Just honest learning.

Let’s Connect

If you’re:

• a student learning web development
• a junior dev working on real apps
• someone who enjoys discussing architecture, security, or clean code

Feel free to comment or say hi 👋
I’m always open to learning from others.

Thanks for reading — this is just the beginning.