Skip to main content

Code is now free, Software is not



I wanted to write this post for several months now, just because of my own experiences and also what I hear more and more from my network. The executive summary sentence goes something like this: "We are again making our own software". What I'm implying with "again" is the fact that throughout the 90s - with client-server, a lot of the software at large companies was built in-house by their own software teams. I'm seeing somewhat of a resurgence of this development but it hasn't come to the large enterprises (yet), it has started with regular people, trying to create their own software for various reasons. For me, it was a combination of cost and gap - for example, I just couldn't find a simple CRM tool that fulfilled my somewhat limited needs, so I wrote my own. Or for years I've been longing for a PFM software package that could reconcile all my accounts - domestic and foreign, it simply doesn't exist for my needs, so I wrote my own PFM. I've tried to wean myself off from Adobe's Lightroom, and thanks to the coding agent, I was able to write all the necessary scripts to essentially re-create the setup in an open source tool. I'm hearing these stories from other people too. Everyone in my circle is building software for themselves.

Here are some of the examples I've created mostly on the side (the CRM and PFM is private so I won't show this):

  • https://swisscompanyresearch.ch - a completely functional Saas portal to research Swiss companies for different use cases (going-concern, general profiling and succession evaluation).

  • https://thedailysignal.ch - this is basically one of my earliest side projects. I started this in April 2025 and the idea was to grab news articles from around the world, synthesise, cluster and then present a summary. The first versions were terrible, the clustering was utter nonsense (lots of trialing) but over the last several months, a somewhat decent harness can now self-correct and essentially "learn" how some articles should be clustered by running these trials completely independently of any human interaction - it then creates code & prompts to improve this. The version that I have now is vastly better because of that.

This new developer-heaven environment has been enabled by improvement in harnesses and large language models - when I started my "vibe coding" journey 1.5 years ago, I predicted that we would have no-code solutions so that everyone could create software, I think we blew past this - we're in a world where anyone without any programming background can now create software in higher languages such as C++, Rust, TypeScript and many more.


But what does it all mean?

Today, we continuously improve the software development lifecycle, with all its governance, roles and responsibilities, but I would argue we will undergo a seismic shift in how Software is created.

Single developer is the bottleneck

 Not wanting to be too technical, but in this new paradigm, the single developer is no longer the bottleneck - everyone else is, because the one thing that scales now very well, is that single developer. I will dare and try to outline another prediction: imagine a world, where we have "outsourced" the whole software development pipeline to agents - a Product Manager agent, an Enterprise architect agent, a solution architect agent, a coordinator agent, a validation agent, a verifier/bugtracker agent, and a shipping/deploy agent. 

The product manager doesn't scale.

In this world, the single human is the person with the vision, the concepts, and the features. This is a new role that combines a product manager with a software architect. However, that single person is now the bottle-neck because this whole pipeline can scale - except for the human in the loop. Therefore, we will have several of these orchestration layers - call them meta-orchestration where humans essentially coordinate the big picture work, and leave the implementation to their agents. 


How will large enterprises make use of this?

I simply don't know but I suspect it will take some time for large enterprises to make this shift; But when they do, software competencies will be a differentiator.


Will this mean we will have less programmers?

No, I think it means we'll have more roles that are a mix of product manager + architect + programmer + project manager. I think the pure programmer role will disappear, as for the other roles, they will evolve. It is important to know these tools. 

But this also brings me back to the title - code is free, but software will not be free - it might be less expensive for companies to create their own software compared to their existing vendor solutions, however, the domain knowledge around the software will be costly. Likewise, for anyone creating software - even if the code is not costing anything, it still takes effort and time to produce. But herein is the beauty because now, the barrier of entry for a lot of people has disappeared, everyone can code now. 

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Vibe Coding Alert! How I Rebuilt a Wix Site and Fed the “AI Will End SaaS” Panic

My better half is an artist and maintains a Wix.com site. For the second time in two years, Wix decided to raise the hosting fees. That’s when I suggested to my spouse that I could rebuild the website and host it on Firebase (where I host most of my projects). I assumed this wouldn’t be a big deal (I was wrong) and started researching ways to use a lightweight CMS with Firebase support. Such a system exists — it’s called FireCMS — and it’s excellent. Before I dive deeper, here’s her original site (no longer a paid Wix site):  Miyuki's WIX site Her instructions were clear: replicate it as closely as possible. So I went to work. I created a product development document with use cases, scope, screenshots from the original site, the required features, and of course FireCMS integration. I used ChatGPT to draft the document, then set up a new Firebase instance, and finally launched the Vibe Coding agent (Claude Code). The process wasn’t too different from my other projects, but what sur...
3 comments
Read more

How I Ended Up Creating an AI Playground to Illustrate and Educate

TL;DR AI Playground User Guide
1 comment
Read more

MCP + Context: engineering for the context – hard lessons learned

  Intro I have built my own orchestration framework because most of what I’ve seen was too complex or tried to lock you into creating workflows a certain way. I wanted something very simple and yet maximally flexible. I’m not going into details here on the framework — that’s another blog post — but I will in some cases explain why I could do what I did thanks to the flexibility of the framework, which is a dynamic DAG, can do call-backs, and uses functions and MCP servers. I will also not explain in detail what I’m doing with my current workflow, other than to say I was looking for a way to bypass large language models and instead run it on my own system at home. I succeeded with that — but that’s another blog post. Instead, what I will try to explain in this post is the most important thing after prompt engineering: context engineering, and why it’s so crucial to manage that aspect (especially when you run this at home). Stage setting A couple of weeks ago, Anthropic posted this: ...
1 comment
Read more