From Frontend to Full-Stack: Starting My Developer Blog
After years of working primarily on the frontend, I’m starting this blog to document what I build, what I learn, and my journey toward becoming a more complete full-stack developer.
I’ve been working professionally as a Software Engineer since 2022, spending most of that time building things for the web.
Over the years, I’ve worked with different technologies, codebases, teams, and projects. My work has gradually become more focused on frontend development, with Next.js and Astro becoming two of the technologies I use most often.
And now, I want somewhere to document that journey.
Why Start a Blog?
As developers, we solve problems every day.
Sometimes it’s something small — a CSS issue that somehow takes two hours to figure out. Other times, it’s understanding why an application behaves differently in production, designing a better component structure, integrating an API, or figuring out why a deployment suddenly stopped working.
Eventually, the problem gets solved.
Then a few months later, we encounter the same problem and think:
“I know I’ve fixed this before…”
That’s one reason I’m starting this blog.
I want this to become a place where I document problems I’ve encountered, solutions that worked, things I’m experimenting with, and lessons I’ve learned while building software.
Not just for other developers, but also for my future self.
Moving Beyond the Frontend
Frontend development is where I’m most comfortable.
I enjoy turning designs and ideas into interfaces, structuring applications, working with components, and figuring out how users interact with a product.
But I don’t want my understanding of an application to stop at the API request.
I want to understand what happens on the other side.
How should an API be structured?
How should authentication work?
Where should business logic live?
How should data be modeled?
How does an application go from a Git commit to something running reliably in production?
Those are areas I’m actively working to understand better.
My goal isn't to move away from frontend development. It's to expand beyond it.
I want to become the kind of engineer who can comfortably follow an application from the interface all the way down to the server, database, infrastructure, and deployment process.
What I’ll Write About
Most of the posts here will probably come directly from things I’m working on.
That means you can expect topics around JavaScript, TypeScript, React, Next.js, Astro, frontend architecture, debugging, performance, APIs, backend development, deployment, and whatever else I happen to be learning at the time.
Some posts might be tutorials.
Some might be solutions to very specific bugs.
Others might simply document something I learned that I think is worth remembering.
I don't expect every post to have all the answers. Part of the point is documenting the process of figuring things out.
Building in Public
There’s always another framework to learn, another architectural pattern to understand, and another way to improve something you built six months ago.
That’s part of what I enjoy about software engineering.
This blog is going to be a record of that progress — what I knew, what I got wrong, what I learned, and hopefully how I improved along the way.
So, this is post number one.
Let’s see where it goes.