We are a team of software veterans. We saw it all. Our dev community is a fluid thing — in the last thirty years, patterns and practices shifted, architecture design followed, new languages popped in claiming they were the best. New services and theories, streams of what is best for a better software design. If you've been around long enough, you start seeing a pattern at every turn. Marketing initiatives selling the new paradigm as the panacea of all struggles. And all of us get excited quite easily. New ideas, new solutions that solve, most of the time, non-existent problems.
And when LLMs dropped from the sky, we suddenly had two contrasting feelings. We can get things done without thinking and fast. And then the epiphany, a few weeks later: oh my gosh, this is going to replace me.
We are big fans of LLMs for coding, we have been using them since the beginning. But we recognised the pattern. The market is getting flooded with tools and services built at incredible speed, and that speed is seductive. But speed alone does not replace the expertise that took years to build. You cannot assume that because an LLM can write the code, it can do the thinking on your behalf. You still need to build the knowledge, understand the trade-offs, and design a process that helps you deliver quality. Our collective contribution over decades led all of us to the world we are living in — and that contribution was never just about typing faster.
Within the next few years we will be watching a plethora of new apps and services, built on the assumption that LLMs could do the job. Half-baked, spaghetti code repositories, leaking data, full of workarounds that simply do not work and cannot deliver the promise. And we are waiting for that moment. Companies will recognise the mistakes, promising again to fix the mess. And we will be there expecting the emergency calls to help them make sense of it all. As it happened in the past so many times.
What nobody told you is that the moment you started working with LLMs, you were being promoted. Your job shifted from writing code to leading something that writes code for you — and that requires structure, judgment, and process that didn't exist before. But neither you nor the company you work for know it yet.
While we recognise that coding is not a bottleneck anymore, and neither is building a POC or a mockup to test ideas, getting to a structured, compliant and future-proof software product takes more than just coding. We need a process while everybody fights against the dopamine of LLMs. And that is the reason we built Swarmix.
We are not VC-funded and we want to keep it that way for the time being. We bootstrapped Swarmix and we are willing to grow with the community. We appreciate that some would like to contribute, and we are keen to define a common path forward where your ideas and contributions can make an impact.
In a probabilistic domain, we want a deterministic framework and foundation that leads us to deliver amazing results. And Swarmix is built for this purpose.
Autonomous systems are not our goal. You are at the centre and you lead the way.
Swarmix is almost ready. Leave your email and we'll send you an access code.