Why I Started Writing After 13 Years in Software Development

For more than a decade, software development has been my profession, my craft, and often my primary way of solving problems.

Over the last 13 years, I have worked with multiple technologies and frameworks across backend and frontend development. My journey has included JavaScript, Node.js, Java, Python, Spring Boot, NestJS, FastAPI, Angular, React, and Next.js. Some technologies became daily tools, while others were used to solve specific business problems. Regardless of the stack, the common theme was building software that delivered value.

In April 2025, I left my full-time position.

Since then, I have spent a considerable amount of time thinking about what comes next.

The Unexpected Challenge

When you're employed, many decisions are made for you.

There is a roadmap.

There are deadlines.

There are customers.

There are business requirements.

There is always a next task waiting in the backlog.

When that structure disappears, something interesting happens.

You realize that freedom can be both exciting and overwhelming.

Suddenly there are dozens of possible directions:

• Build a SaaS product
• Start a technical blog
• Create educational content
• Launch a YouTube channel
• Offer consulting services
• Explore new technologies
• Build tools for developers

The challenge is no longer writing code.

The challenge becomes deciding what deserves your attention.

Why This Blog Exists

This blog is my attempt to turn years of experience into something useful and publicly accessible.

Over the years, I have made mistakes, fixed production issues, redesigned systems, rewritten code that should never have been written in the first place, and learned lessons that no documentation page could teach.

Many of those lessons exist only in my memory.

This blog is where I intend to document them.

I plan to write about:

• Backend architecture
• API design
• Node.js and Python development
• System design decisions
• Deployment and infrastructure
• Lessons learned from real projects
• Technical mistakes and how to avoid them

My goal is not to create generic tutorials.

There are already thousands of tutorials on the internet.

Instead, I want to share practical engineering experiences that come from building and maintaining software over a long period of time.

What You Can Expect

The articles here will focus on real-world development rather than theoretical examples.

Some posts will be technical deep dives.

Some will be architecture discussions.

Others may cover career decisions, independent development, and the realities of building software outside traditional employment.

Most importantly, I will write consistently and honestly about what works, what doesn't, and what I learn along the way.

The Next Chapter

This blog is also a personal commitment.

Not to build the perfect website.

Not to launch the perfect product.

Not to have all the answers before starting.

Simply to start.

The internet rewards people who publish, learn, and improve in public.

After spending years building software for companies, I'm interested in seeing what happens when I build something for myself.

This is the first step.

Thanks for reading.