The token cost to build a production feature is now lower than the meeting cost to discuss building that feature.
Let me rephrase.
It is literally cheaper to build the thing and see if it works than to have a 30 minute planning meeting about whether you should build it.
It’s wild when you think about it.
This completely inverts how you should run a software organization. The planning layer becomes the bottleneck because the building layer is essentially free. The cost of code has dropped to essentially 0.
The rational response is to eliminate planning for anything that can be tested empirically. Don’t debate whether a feature will work.
Just build it in 2 hours, measure it with a group of customers, and then decide to kill or keep it.
I saw a startup operating this way and their build velocity is up 20x. Decision quality is up because every decision is informed by a real prototype, not a slide deck and an expensive meeting.
We went from “move fast and break things” to “move fast and build everything.”
The planning industrial complex is dead.
Thank god.
@nejatian Mobile forces sequencing. Best UX I've seen: chat as primary surface with action cards inline, structured UI via bottom sheets (Vaul/shadcn). Sheet slides up over chat - you can see context underneath.
Apple Maps nailed this for location details. Same principle applies to chat.
@dzhohola Nope, no docker needed - it's lightweight and runs in the terminal. The heavy lifting happens on their servers.
Just run 'claude --dangerously-skip-permissions' to go autonomous.
The key is having a solid prompt file to set the proper scope/guardrails.