Ogre's Kitchen
No repository. No subdomain. No implementation. The name has nevertheless survived every opportunity to kill it.
I wonder what happens if an ogre opens a restaurant.
Well… Why not?
SubZeroDev was always meant to be a business.
We just never decided what kind.
There was no master plan.
No product roadmap.
We built things because they were useful, interesting, or both.
One problem became a solution.
One solution became infrastructure.
Infrastructure became a platform.
Some things became products.
Others escaped and became entirely different things.
We don't force ideas to fit the business.
We let the business follow the ideas.
We do the next interesting thing well.
Then we see what happened.
The absence of a plan is the plan.
Effortless Action.
No repository. No subdomain. No implementation. The name has nevertheless survived every opportunity to kill it.
I wonder what happens if an ogre opens a restaurant.
Evidence that a conventional portfolio was considered before considerably less conventional things happened.
I suppose I should have a portfolio?
An attempt to replace an increasingly expensive stream of automated code reviews with an increasingly elaborate stream of our own.
Why am I paying this much for something an agent can probably do?
Container management tooling for the point where remembering which machine is running what stops being a viable operating model.
What's actually running where?
Documentation infrastructure for projects that would otherwise eventually contain a README written under duress.
I wonder if documentation could maintain itself.
Turns Git repositories into an API, workflow surface and MCP capability because apparently Git needed another abstraction layer.
What if agents didn't need direct filesystem access to work with repositories?
A resort-management satire where guests, plumbing, weather and basic geometry have formed an alliance against management.
What happens when a resort simulation is allowed to behave like an actual resort?
A control plane for publishing because apparently writing a blog post eventually requires a server protocol.
Why shouldn't an agent be able to publish this?
Build and release automation extracted from repeatedly teaching repositories how to perform the same ceremony.
Why does every repository need to relearn how to build itself?
Hosting, configuration, identity, notifications and observability extracted when several unrelated projects independently demanded the same machinery.
Why am I building this again?
The first implementation of the plugin contract, subsequently sentenced to becoming the template for all the others.
What if GitHub were just another capability behind a contract?
Repository-installed agent infrastructure that eventually became capable of finding bugs in itself and filing the paperwork.
What if the repository could tell the agent how to work here?
Loads structured data from HTTP or files. Started inside Docs Template and escaped into its own package when apparently reading JSON needed infrastructure.
Why does every project eventually need to load the same JSON in a slightly different way?
Watches containers because apparently keeping software alive also became software.
Who watches the containers?
Started with one question about an old game. Somehow became a deterministic engine for building mechanics once and games repeatedly.
I wonder how Jones in the Fast Lane actually works.
Turns container commands into PowerShell modules because remembering docker run arguments is not a personality trait.
Why am I typing this command again?
Started as somewhere to publish a blog post. Acquired workflows, automation and infrastructure before anyone intervened.
I need somewhere to publish my blog.
A C# wrapper around the WinGet COM API because parsing winget.exe output was never going to become less ridiculous.
There is a COM API. Why are we parsing console output?
The environment every new machine receives before it's trusted with repositories, tools or opinions.
Why does setting up a development machine still involve archaeology?
Field reports from reality, narrated by Lucifer because ordinary documentation proved inadequate.
What if the absurd parts of life were documented completely seriously?
We asked for a quote. We received a philosophy.
Delivery was on time. I have been unable to establish what the plan was.
The documentation is excellent. It is also longer than the software.
I asked what the roadmap was. They told me the absence of a plan is the plan. Twice.
I requested a minor website change. Three days later they had built a game engine.
Technically they delivered everything we asked for. This somehow made the experience worse.
They are using our staging cluster. We do not have a contract with them.
They refactored the invoice.
I don't work here. They keep putting me on the website.
I cannot determine what they sell. My analysis is ongoing.
Their agents opened forty issues overnight. Two of them were mine.
They came to our village. We now have observability.
Their deployment process frightens me, and I have fought Thanos.
I find their lack of project management disturbing.
Hire them, you should not.
Four score and seven abstractions ago, this was a small change.
I have read their contract. It is longer than mine.
I gave humanity free will. SubZeroDev is making me reconsider.
Vision doc says "two kinds ship in v1"; the repository ships three
You declined to predict a single thing. This is, statistically, the single most reasonable choice available in this entire campaign, and reasonable was never really the point.
Lucifer, for what it's worth, would probably respect this. Briefly. Then he'd build something about it.
PROGRAM LOADED. YOUR STORY BEGINS HERE.
THIS MATTER HAS BEEN CONCLUDED WITH EXCESSIVE CEREMONY.
START ANOTHER RUN