// TL;DRDiscover my personal journey from frontend developer to full-stack developer. Learn about the challenges, growth, and rewards of expanding your skills from React/Next.js to .NET APIs and MySQL.
I never thought I'd be working as a full-stack developer. When I started my journey, I was completely focused on frontend development with React and Next.js. My passion was building clean UIs and delivering smooth user experiences.
// 01From Frontend to Backend
Over time, opportunities came up to step outside of my comfort zone. I began working with .NET APIs and MySQL databases. At first, it was uncomfortable — debugging SQL queries, handling API errors, and learning backend workflows felt frustrating.
But slowly, that discomfort turned into growth.
// 02Becoming Full-Stack
Today, I'm able to contribute across the full stack:
- /Frontend — React & Next.js for building intuitive UIs
- /Backend — .NET APIs for logic and scalability
- /Database — MySQL for structured data management
This shift hasn't been easy, but it's been the most rewarding part of my career so far.
// 03Specialist vs. Full-Stack: What's Better?
Every developer's journey is different. Some love diving deep into specialized roles (frontend or backend), while others thrive as full-stack developers who can handle it all.
- /Specialist approach — deep expertise in one area, focused skill development, clear career progression, mastery of specific technologies.
- /Full-stack approach — broad understanding of the entire stack, versatile problem-solving, end-to-end project ownership, adaptable to different roles.
There's no right or wrong answer — it's about where you find your passion and how you want to grow.
// 04Over to You
Do you prefer specializing in frontend/backend, or going full-stack? Share your perspective — I'd love to hear your story!