Yes, you read that right. I killed the backend of my project, and I did it with zero regrets. Let’s talk about why.

In a world where we, as developers, are often pressured to add complexity to our systems — more layers, more services, more integrations — I decided to go the opposite way. I decided to simplify violently.

The project in question is called AutoMenu, a service I built two years ago that powers several coffee shops in the Vale do Paraíba region. It used to run on a robust headless CMS (Strapi), with a full backend setup that I spent countless hours maintaining. But one day, I asked myself: Why am I dedicating so much energy to maintenance when I could be focusing on what really matters?

So, I did it. I shut down the backend. 💀

Why Google Sheets Replaced My Database

Here’s where it gets interesting. I replaced the entire backend with… Google Sheets. Yes, a simple Google Sheet where clients manage their products, and a single codebase hosted on Vercel using Next.js handles everything, from front-end to back-end logic.

And before the complexity enthusiasts lose their minds, let me explain: It works. The system doesn’t process payments or require ACID compliance, so why over-engineer it? Instead, I validate and cache data efficiently with Next.js route handlers, making it lean and maintenance-free.

The Philosophy of Violent Simplification

✨ Creating is gold, but maintaining is diamond. ✨ And every line of code you write is a future liability. Maintenance is a time sink that traps you, eating up your energy and freedom. The more complexity you add, the more you have to manage — and the more chained you become to your project.

This isn’t just a technical decision; it’s a strategic one. Companies could benefit massively from adopting a similar mindset. Imagine cutting down on unnecessary microservices, bloated databases, and overly complicated architectures that don’t deliver measurable value.

When to Say No to More Features

I face constant pressure to add things like user data collection and payment processing. But here’s the thing: Every feature needs to justify its existence. If it’s not bringing at least double the revenue or solving a problem worth 10X the effort, it’s a distraction.

And distractions are expensive. They turn simple systems into high-maintenance monsters. Most businesses aren’t willing to pay for that level of complexity, and I refuse to sacrifice efficiency for the sake of feature creep.

A New Movement: Intelligent Simplification

I’m calling for a movement. A push to simplify with ruthless intelligence. To cut out the fluff and streamline systems from day one. This isn’t laziness; it’s strategic thinking. Use your IQ to design lean architectures that deliver value without drowning in maintenance.

Think about it: Do you want to spend your career fighting fires in overcomplicated systems, or do you want to simplify and focus on what really matters? Simplifying violently is not just about less code — it’s about more freedom, more focus, and more impact.

So, let’s have this conversation. Are you ready to kill the unnecessary parts of your projects and embrace simplicity? Or will you keep adding complexity for complexity’s sake?

💬🔥 Let’s debate. Because sometimes, the boldest move is to simplify violently — and live freely