Why I stopped chasing the trendy stack everyone uses
A few years ago, I felt constant pressure to adopt the right stack. Everyone was talking about the tool or framework of the moment, and it seemed like anyone not using it was wrong. At first, I tried to keep up and thought maybe I was falling behind.
Over time, I understood a simple but liberating truth: the industry doesn't exactly know what I'm building or what my constraints and priorities are. That idea made me stop and rethink my approach.
What I really needed
I work on small and medium-sized web applications, sometimes for clients and other times for my own projects. I don't need Kubernetes or piles of configurations for every project. What I do need is a simple backend that works, forms that process data, a design I can style quickly, and something I can maintain on my own and deploy with agility.
You don't need a spaceship; a scooter is enough for me to deliver value fast.
I built my own tool
Instead of chasing tools I didn't enjoy, I developed something I do enjoy using. I called that set VeltoPHP. It's not huge or flashy, but it makes sense for my projects and lets me move without depending on too many updates or breaking changes from third parties.
It's not about being better than solutions like Laravel in absolute terms. It's about choosing what's best for my workflow and my goals.
The best stack is the one you understand
I've seen criticism of PHP, jQuery, and other not-so-trendy technologies, but I've also seen independent developers create profitable and solid applications with those same tools. Most of the time, best practices are simply what works best for each person or team. If you understand your stack and can move fast with it, that's your stack.
Stop telling others what they should use
We build very different things: large teams, solo developers, startups, and side projects at night. It doesn't make sense to impose a single solution on everyone. It's more useful to ask about goals and constraints and recommend options that allow delivering results.
Idealism versus fanaticism
I admire those who care about architecture, patterns, and performance, but there's a line between sharing knowledge and forcing an opinion. Confusing idealism with fanaticism leads to echo chambers instead of useful communities.
What really matters
In the end, I want to be remembered for what I built and the problems I solved, not for the technology label I put on a project. The best technology choice is the one that lets you ship, learn, and scale. Choosing the right stack for your needs is a wise decision, not a disqualification.
About Q2BSTUDIO
At Q2BSTUDIO, we are a custom software and application development company specialized in creating practical and scalable solutions. We offer custom software services, applied artificial intelligence, cybersecurity, and consulting in AWS and Azure cloud services. We help companies implement business intelligence services and Power BI solutions to make data-driven decisions.
Our approach is pragmatic: we design AI agents and AI solutions for companies that meet real goals, integrating good security and cloud operations practices. If you need a custom application, an artificial intelligence project, or to improve your cybersecurity posture, at Q2BSTUDIO we can accompany you from prototype to production deployment.
Final message
It doesn't matter if you use PHP, Go, Ruby, or Vanilla JS. What matters is that you build something that makes sense for you and your users. If you're delivering value and learning along the way, you're on the right track. And if someone tries to impose their stack, remember you don't need their permission to build your own way.
What about you? Have you felt pressure to use a specific stack, or are you already charting your own path? At Q2BSTUDIO, we're interested in hearing your story and exploring how we can help with custom applications, custom software, artificial intelligence, cybersecurity, AWS and Azure cloud services, business intelligence services, AI for companies, AI agents, and Power BI.
