Around 2 months ago, I saw the limitations of NLC.
When it comes to agentic engineering, its easy (and tempting) to keep adding new functions and features.
The sexy ones.
The ones that make people go “wow!” and get lots of attention.
Its very tempting to just create sizzle reels off the 10% times that things do work, talk about all that things that the product can do while conveniently hiding things it can’t.
But the reason why I won’t is because NLC wasn’t built for ‘everyone.’
It was built for me and people like me.
Nothing in the market has what I need without having to stitch together apps from dozens of different sources.
I wanted everything that I will ever need, under one roof, capable of producing the output of an entire corporation.
One human deciding the direction, with an army of AI agents doing my bidding.
Yes, there’s a lot of these “AI employees” concept going around these days…
…but many of them are employees in name only.
You can’t really rely on them the same way you can rely on humans.
I want generals, not infantry.
I want things that glues all of them together, not be the glue myself.
NLC is my vehicle, and to prove that it works, it needs to be able to do all of that for me.
2 months ago, I encountered that limit.
NLC was “fine” - but fine wasn’t good enough.
I got to work and announced that I am creating a major “stability update.”
That same update took so much work, it is now becoming NLC 2.0.
While that was happening, however, my customers weren’t getting updates.
Reason is that while I dogfood my own creations, my own copy of NLC that I am using is simply a huge mess of bugs.
Not production ready.
So shipping stopped because I need to make the changes on my main copy, and ship that copy to everyone else.
For a long time, that weighed on me.
And then I discovered the concept of a ‘hotfix.’
Basically:
If there is a bug, make the fix in the customer machine directly instead of on my machine
If there is a feature request, make the changes in their machine instead of mine
Merge the changes to the latest stable version instead of my own copy
Roll it out fleet wide
I quickly established a protocol for that a few weeks back, and proved it on the same day.
Today, I compiled 35+ stabilization updates I’ve made over the weeks and shipped the whole thing.
So stabilization update: Mission Accomplished.
But in the pursuit of this mission, I realized there are so many more things that I need to do in order to realize my vision of a 1 man corporate army.
And so, the next mission is to finish NLC2.
Since a lot of the work has been ongoing for the past 6 weeks however, I am glad to say I am not starting from scratch.
I will be updating you guys on my progress as I go.
Doing this, I also realize there are so many things that vibe coders really miss when they are building their apps and so on.
If I with all my experience with AI could get my ass kicked in real production work, I imagine the same might apply for many others too.
So I’m thinking to run a class on agentic engineering, sharing everything I’ve learned so far about building with AI.
Frameworks, processes, how to manage agents, etc.
Would attending said class be of interest to you?
Hit reply and let me know.
FELIX