One of my favorite quotes that I've tried to live by for decades is: "If somebody offers you an amazing opportunity but you are not sure you can do it, say yes - then learn how to do it later!" ~ Richard Branson
In the time that I have been active on social media, I've seen some pretty amazing things developers are creating, and I am both inspired and a little bit envious. It is one of those situations where I wish, "I could do that," but as established in some of my #30in30 articles, it is not possible to learn everything.
In the world of development, few topics ignite as much passion as the choice of tech stacks, CMSs and tools. Every day, I read along my timelines and see it - the tension between stack loyalists. One group might argue that PHP is dead, while another derides JavaScript frameworks as an endless rabbit hole and don't even get me started on the AI debates. Why does it matter so much which stack, CMS or tool is "better"?
I've come a long way by learning as I go along. Ultimately, the stack you choose is about you, not your client. It’s an identity, a badge of expertise, and sometimes, a line in the sand. At the end of the day, the client wants a complete, functional product that is user-friendly and usable. They don't care how you do it, just that the product delivers on their expectations. Most clients do not even know what you're talking about when you talk stacks. If there is one lesson to learn, never overwhelm a client with lingo - always explain things to them in layman's terms.
Many years ago, I worked with Joomla. There was (almost) nothing I could not create with Joomla. I wrote custom themes and plugins in PHP and created anything from simple guesthouse websites to complex real estate websites that required the implementation of web services. Then one day, I was commissioned to create a hotel website, and the client anxiously called me in - another WordPress web designer (who I knew) heard that they wanted to redesign their website and told them that they should not work with me because I design "dangerous" websites! The client asked me to explain what he meant and why I was using Joomla instead of WordPress.
Before the meeting, I wrote the client a letter detailing that, ultimately, the CMS and tools a developer decides to use depend on the project and are at the discretion of the developer. We choose the best tools for the job and side with what makes our lives as developers easier. At the end of the day, the client will receive a stunning and functional website with a custom dashboard for easy updates, which is exactly what they wanted. I sent them screenshots of the custom dashboard vs. the overwhelming WordPress dashboard, as well as a screenshot of a Google search: I searched for "Joomla vulnerabilities" and received pages of WordPress vulnerabilities and issues, including an FBI advisory. No Joomla results were listed. During the meeting, I cleared up some remaining concerns and confusion and received the go-ahead for the website.
Never be that guy. This is a perfect example of professional jealousy, and it is not good for the industry or for the clients. We are all superstars in our own way - you do you, and if you excel at what you do, your stack, CMS or tools of choice do not matter. You'll shine and get the jobs. And there are enough jobs for everyone out there.
I have since moved on from Joomla to October CMS, which is built on Laravel. I work with WordPress as well, but to be honest - I hate it. With passion. I only work with WordPress on request. But that's my personal preference and choice. It does not mean that WordPress is bad or that there is something wrong with WordPress designers. It just means I found something out there that is a good fit for me. Working with something that frustrates you will take all the joy out of being a developer.
I've also seen some negative conversations around October CMS, which stem from the introduction of a paid licensing model with version 2 - it alienated some users who were accustomed to the free version. From this, Winter CMS was created, which continues with free, open-source development. October CMS targets developers rather than general users, and its requirement to understand Laravel and Twig can be a hurdle for non-developers.
But I appreciate the developer-first approach with a Laravel backbone that makes October CMS powerful and flexible. It allows for clean, modular development without excessive bloat, and I find it faster and more secure than many other CMS platforms. I particularly love the rapid application development features. With the power of Laravel and October CMS, I can craft a website of any complexity and provide the client with a custom solution that is sleek, user-friendly, and usable. They don't have to know what's under the hood - they just get to drive the car.
I appreciate a development ecosystem where a PHP developer can learn from a React expert, and vice versa, without ego or judgment. Every stack and CMS has its strengths and weaknesses, and no single tool is perfect for every scenario.
And so, to all developers, I say this: Let’s build bridges, not walls. Let’s choose curiosity over criticism, respect over rivalry. Together, we can create not just better software but a better community. Because in the end, it’s not what we choose to use that defines us; it’s the solutions we create and the connections we forge that truly matter.