Wubbleyou’s Post

“What is your tech stack? Competitor X says theirs is better/cooler” Boring tech stacks make our customers a lot of money. Plus, our modern tech stack is cool to us and not boring. Conversely as another founder put it: “We’d let devs have fun with new frameworks, and then spend years maintaining a product in some alpha JavaScript framework that’s no one has ever heard of” If Competitor X is proficient and using a modern tech stack different to ours, both are likely equal, and neither is better. If Competitor X is building your business-critical platform in some cutting edge, new to market framework, it will be cool for about 3 months and then be a total slog to maintain. The sort of codebase you take to another tech partner and they want to rewrite it. Plus, your customers don’t care – they want to use a product that adds value to their life. They don’t care that some techy in a hoodie like me says the code looks really nice. I think what really matters, is that your tech partner does the following: ✅ Uses a modern tech stack, and knows it inside out. They are really good with it, like really, really good ✅ They focus on building tech to create value for you, and solve your problems Building a really cool product that no one wants to use, is a big waste of time and money. There must be a big emphasis on discovery and what business success looks like before building a tech product. How do you measure the product is successful? How do we gear the product to achieving that? Wubbleyou does this very well. For our stack, at Wubbleyou we use Laravel, Vue, Tailwind, MySQL, deployed into a highly scalable AWS configuration using a Terraform recipe we’ve iterated over the years. We can solve a lot of problems quickly with this method. Sure, we use Golang, Python, NodeJS etc when there is a sharp problem we need to solve where another language has a clear edge. For example, for computation speed, Golang can win, Python for data analysis or solving hard optimisation problems, Node if someone has already solved your problem and made a library for it 🤷 Tools in a toolbox. Otherwise, we’re using a tried and tested stack that has a long life ahead, which we know is capable of building tech products which service millions of users and generate millions in revenue. All things equal, I think “which partner’s tech stack?” is only a considered question if you have an existing tech product, and you’re keeping everything in one stack for maintainability.