It doesn’t matter how fast your code is generated if the requirements are unclear. Shit in == shit out. That’s why we designed Software Factory as a discipline, not as a convenience tool. Our agents scrutinize your requirements and designs so that when you pass that context to a... coding agent, it delivers as expected. Try it here:show more

Measure twice, cut once…

I mean this with zero malice: if you’re a billionaire, why are you spending time working on an AI SaaS?

I like trying to help make useful things when I think they could matter. I think making a factory for people to use as we go through the AI revolution feels like one of those moments. Whether it will have been a good use of time will only be known after the fact…

Fair enough!

genuine question... what's stopping me from running gpt + gemini deep research on my requirements then feeding the security gaps to claude code? already paying $400/mo for these tools...why add another layer?

Nothing is stopping you. If it works for you, keep with it.

curious - where can i send you my decks ?

Planning is as critical as execution with coding agents. We found same insights for spec driven development. We built our own software factory for optimizing database software.

“Shit in, shit out” is true; but most requirements are unclear because teams avoid making tradeoffs.

How does this challenge the requirement when often the individual providing the requirement is unclear. Does this require a prompt engineer (middle man)? Replacing workers not completely with AI but with someone who knows how to use AI?

It allows many people to swarm the requirements phase so that knowledge quality goes up. We designed this to be used in a broad team.

I’ve got a project to test this on. Who do I talk to.

we've been saying 'shit in, shit out' for decades but finally having an agent with the spine to say it back to the stakeholders is the real productivity hack

Exactly bruhhh.... Speed doesn’t fix confusion. If requirements are fuzzy, faster code just means faster bugs... and the hard part of software was never typing code, it’s thinking clearly, agreeing on intent, and locking decisions before execution. Automation without clarity just scales mistakes...

curious how deep the scrutiny goes

@chamath have you guys discussed Ralph Wiggum Loop for the product ?

yeah my team once wasted three weeks debugging ai-generated code that perfectly executed the wrong idea

This seems cool! I spend most of my time writing and refining specs. Having at least a substantial portion of the architecture and code written and reviewed spec files is the only way I've been able to get consistently good results.

I still prefer the term GiGo

Ownership of generated code? Portability or platform lock-in? Price of tokens for planning and coding?

Cant this be created into a claude skill?

Any thoughts on making individual subscription? Startups?

is there significance to the number 8090?

Precisely. And this is the most underrated thing about prompting. We’ve been given ai tools with the promise that it can solve all our problems but we have limited training and know-how on using the tools optimally. Tools with built-in checks points and quality gates makes perfect sense to me. It’s always one step ahead in the pursuit of delivering actual value. The tool should know what I want to do and recognize I do not know how to arrive to the desired outcome. Ai should be curious about what the operator is trying to do. And make itself useful in solving the proposed problem. Much like how humans (some) are intrinsically curious and are problem solvers.

Good design something to look at market makers dark pools and prime lenders. Yiu know the racket. You've made enough. Liquid some assets for 2 generation and be a hero we all need. CAT System now!

Change the name to much overlap with @FactoryAI

You guys should build this as a wrapper around the coding cli tools like codex so that developers can use their credits to power these features.

I was hoping for an open source version tbh

Been saying this for twenty years. No amount of tooling fixes a bad spec.

Where is 8090.molt?

When do you think all the team sitting in offshore ODCs looking and handling all the SDLC of enterprise software code shall be downsized to single digit team members? I am just thinking on the lines when this kind of 100% automation seep in SDLC liberating teams holed up in desk 24x7, yeah sort of going mainstream for enterprise code

I have two favorite tee shirts. MicroTrash why are you still buying garbage ? And MicroCrap why are you still buying shit ?

so because your requirements are vague, you blame the code? sounds like you need better specs, not a magic tool. reality check: garbage in, garbage out.

AI didn’t eliminate the need for thinking - it made thinking the constraint. Faster code just amplifies whatever clarity (or confusion) exists upstream.

Treating software as a process rather than just a tool is the correct way to think about it.

Clear thinking first, code second.

me explaining my feature requirements: "make it good but like, you know what I mean" claude: *generates 47 different interpretations of "good"*

This can be done with a claude SKILL

Speed is cheap. Clarity is rare. Requirements are the contract between imagination and reality. If you cannot explain the outcome in plain language, you are shipping guesses. Code only amplifies whatever you asked for.

$200/person/month? SAAS? Do this with Git, $20/person/month Claude Code and @nimbalyst Claude Skills, Local, no lockin, open standards.

codex drop just mogged.