Evolving Code, Preserving Values: Our Journey of Codebase Upgrades

Not too long ago I wrote an article on medium Building in Public a SaaS Platform for Creating, Optimizing, and Deploying Websites on the Cloud: Stacking.Cloud— Part 1 about stacking.cloud and the way we were building it. During this period we built it, and before the private beta to our selected early adopters we just built it again. It may sound dumb but when I build something I feel like an artisan who is building his own artcraft and I want my product to not be perfect but be good. The system we first envisioned just wasn’t that good, it relied on an API to deploy and it needed an additional database, an additional server, and many additional complexities that just weren’t necessary.

In the ever-evolving landscape of technology, the only constant is change. But as we brace for this relentless tide, it’s crucial to remember that upgrading a codebase isn’t just about keeping up with the times; it’s about respecting the philosophy that originally set us on this path, our philosophy is simplicity. Simplicity, not out of laziness but, out of passion and capability to be able to dynamically make changes, fix and adapt to our users’ needs, yours.

Simplicity as Our North Star

Our guiding principle is simple: Does this change make our codebase more comprehensible, more maintainable, and ultimately, better for our users? This is the main reason why we chose to move our deploy logic back to PHP. This move allows us to upgrade the quality of our codebase, and even if you are not able to see this, it’s still there. Like when you buy a Rolex, in your lifespan you will probably never see all the small cogs and pieces under the quadrant that make that watch so precise and precious, but they are still there and they are part of the reason why that clock it’s so good, our code it’s the same.

One of the biggest temptations in software development is to over-engineer, to add layers of complexity because we can, not because we should. We found that a simple solution that works is infinitely better than a complex one that’s a marvel of engineering.

The Human Aspect of Code

Technology is not just about code; it’s about the people who write it. Upgrading a codebase is also an exercise in upgrading our team’s skills and knowledge. We invest in our people, providing them with the resources and learning opportunities to grow alongside our technology. It’s a symbiotic relationship: as our codebase evolves, so do we. This means that, while we made you wait a bit more for the product you get a more mature and tested system made by a team that it’s always getting better just to build a better product for you.

Looking Ahead

As we look to the future, we’re excited about the possibilities that new technology brings. But more than that, we’re committed to staying true to our principles. We’ll continue to evolve, but on our terms, ensuring that every upgrade, every change, reflects our dedication to simplicity, clarity, and practicality.

In conclusion, upgrading a codebase is more than a technical endeavor; it’s a reaffirmation of our values and principles. It’s about striking the right balance between embracing new possibilities and staying true to what’s always worked for us. As we continue on this journey, we remain committed to delivering software that’s not just powerful, but also a joy to use and a reflection of what we stand for.