The studio journal · July 2026 · 6 min read
Vibe coding, community, and building in the open
Twenty-eight days ago I turned a camera on and left it running. The stigma around how I build never survived contact with what it actually takes.
Twenty-eight days ago I turned a camera on, and I have not turned it off since.
It started as a plain experiment. Point a camera at the actual work, post it every day, and let people watch a studio get built in real time instead of reading about it once it was finished and tidy. No script. No highlight reel. Whatever the day actually held stayed in.
I did not expect the month to move the way it has. I started this with fairly basic technical footing, and in twenty-eight days I have taken on real clients, mapped out an entire suite of products, and actually built the things that had been sitting half-formed in my head for years, because I never had a way in. Drop the barrier low enough and the pace changes completely.
The best part of the month has not been the tools. It has been the people.
Posting the work before you know whether it holds up leaves you exposed in a specific way. There is no hiding a rough idea once it is already public. But that same exposure is exactly what put me in front of them: some of the most genuine, patient people I have come across in any field.
There is a whole layer of builders out there who would rather hand you what they know than protect it. They teach instead of gatekeep. If that describes you and you are reading this, you are a large part of why the camera stayed on.
There is a whole network of people out there who want to see you win, not watch you fail.
Now the part I am done tiptoeing around. I am tired of the stigma around how I build.
These tools have been part of the real workflow for years now. They are not a fad passing through. They are part of the foundation, the same way a compiler or a text editor is part of the foundation. And still, read the comments under almost anything built this way and the same word shows up: slop. More often than not, the person saying it loudest has never built anything this way, or any way.
What gets flattened into a joke is a caricature: type one sentence, watch a finished product fall out the other side. That was never the real shape of it, and it has not been close for a long time.
The headline, and what is under it
From the outside it looks like one sentence in, a finished thing out. That is the whole caricature, and it is where the word slop comes from.
The prompt is the smallest part of the job. The actual work is judgment: knowing what to test, what to throw away, what looked finished and quietly was not, and running that pass again and again until something holds under real use. That is not a shortcut around craft. It is craft, aimed at a faster material.
People fear what they do not understand, and it is easiest to dismiss what you have never tried yourself.
I understand the reaction. Watching something change fast and not trusting it yet is natural, and I would probably feel a version of it myself if I were watching from outside. But here is what gets lost in the noise.
Right now, the industry is bleeding. There have been sweeping layoffs across tech, and a lot of genuinely skilled, careful people are out of work through no fault of their own. Real mortgages. Real families. Real fear at the kitchen table.
In a stretch like that, tearing down the tools that hand people a way to build for themselves is exactly backwards. For a lot of people this is not a shortcut. It is a lifeline. It lets someone spin up something real, test it honestly, and support themselves without an enterprise budget or a floor of engineers behind them.
For a lot of people right now, this is not a shortcut. It is a lifeline.
That is exactly the shape of the thing we are building next, and I am not going to pretend otherwise. Datum is a social progression world for the hardest stretch of a career: short AI-assisted sequences in code, language, and multimodal work, leveled by what you actually ship, held in small rooms, stored in a zero-knowledge vault. The Auditor verifies. You confirm every draft. Recruiters arrive on your terms, and they never browse your profile.
We did not build it in spite of this moment. We built it for this moment. A lot of good people are being let go right now who did nothing to deserve it, and the same tools that made this month possible for me should be aimed at exactly that problem, not saved for people who already have a safety net under them.
Call it vibe coding. Call it slop, if that is the word that lets you feel better about it.
I am going to keep calling it building, because that is what it has been for twenty-eight days straight: camera on, work posted before it was finished, the mistakes left in.
Here is to the next twenty-eight days.
Datum is the next room, and the current launch lane: shown before it is finished, and aimed straight at the people who need to rebuild the ability to build right now.
Start a sequenceThe camera is still on. The unedited day-to-day of building Martori lives on TikTok and Instagram.
The studio writes as it builds. If something here maps onto a problem you are carrying, the practice is how we work with people, and the Sketch will draw you a first roadmap in about a minute.