And why that's been the best decision I’ve made for my productivity.

A few years ago, I remember feeling this pressure.

Everyone was talking about the "right" stack to use.

• You must use React.

• You have to build with Docker.

• If you’re still using PHP? “Yikes, bro.”

At first, I tried to keep up.I thought maybe I was falling behind. Maybe I was doing it wrong.

But the more I tried to force myself to follow the “industry standard,” the more I realized:

The industry doesn't know what I’m building.

So I stopped.

What I Actually Needed

I work on small web apps. Sometimes for myself. Sometimes for clients.Most of the time, I don’t need Kubernetes. Or TypeScript. Or an entire CI/CD pipeline just to post a blog.

What I do need is:

• A simple backend that runs

• A form that works

• A layout I can style quickly

• Something I can ship fast and maintain alone

That’s it. I don’t need a spaceship. I need a scooter.

I Even Built My Own Framework

Yeah. Instead of chasing tools I didn’t enjoy, I built something I actually like using.

I called it VeltoPHP. It’s not big. It’s not fancy.It’s just something that makes sense for me.

Why?

• Laravel was powerful, but too heavy for what I wanted.

• I didn’t want to depend on updates or breaking changes from packages I don’t use.

• I wanted to enjoy building again.

Is it better than Laravel? Nope.Is it better for me? 100%.

A Great Stack Isn’t the One Everyone Uses — It’s the One You Understand

I’ve seen people throw shade at PHP, at jQuery, at whatever’s not trendy.I’ve also seen indie developers build solid, profitable apps with those exact tools.

And that’s when it hit me:

Most of the time, “best practices” just mean “what works best for me.”

If it works, it works.If you understand it, and you can move fast with it — that’s your stack.

Stop Telling People What Stack They Have to Use

We all build different things.

Some of us work in big teams.Some of us are solo developers.Some are launching startups.Some are building projects after work with limited time and energy.

Why should we all use the same tools?

Why should we shame someone for choosing something they are comfortable with?

Idealism Is Cool — As Long As It’s Not Fanaticism

Look, I love seeing developers who care deeply about clean architecture, patterns, and performance.But I also think there’s a line between sharing knowledge and forcing opinions.

Not everyone has the same goals.Not everyone has the same constraints.

The moment we forget that, we stop building community — and start building echo chambers.

What Actually Matters

At the end of the day, I don’t want to be remembered for the stack I used.I want to be remembered for the things I built — and the problems I solved.

The best tech choice is the one that lets you ship, learn, and grow.

No stack will magically make you a better developer.But choosing the right stack for your needs? That’s wisdom.

Final Thoughts

I don’t care if you're using PHP, Go, Ruby, or Vanilla JS.What matters is: Are you building something that matters to you?

If the answer is yes — you’re doing great.

And if anyone tells you otherwise, just remember:

You don’t need their permission to build your way.

What About You?

Have you ever felt pressured to use a certain tech stack?Or are you already walking your own path?

Drop a comment — I’d love to hear your story.