Using this for testing... it feels like a sweet spot between in-memory SQLite and spinning up a full Postgres instance. I'd been looking for this for a while and I'm pretty happy with the faster tests. And so far no blockers from its limitations.
I'm using conductor.build and running both Claude Code and Codex. It's taken 95% of my workflow and I'm loving it (I'm not affiliated with them at all, genuinely enjoying it and hoping it succeed)
Same here. Codex support is a recent addition however, and it’s not clear if MCP servers and other rules apply to Codex. Also it would be nice to be able to just have a session working on the main branch as concurrent work in worktrees can get messy
I hope this reaches other companies selling to technical people. I’ve also been a CTO at a $xxM ARR company, and I made several buying decisions for competitors who let me try their product without requiring a meeting.
Of course, some people do prefer calls, but I think there’s a disproportionate default to “book a call first” when selling.
You are forgetting marketing is temporal. Fifteen years ago you could sell your software as the Cloud version of a legacy app. Right now, there's a window that being the AI version will get you a call.
"Drift to low performance is a gradual process. If the system state plunged quickly, there would be an agitated corrective process. But if it drifts down slowly enough to erase the memory of (or belief in) how much better things used to be, everyone is lulled into lower and lower expectations, lower effort, lower performance."
The pivot of the century? Starting with a failed mining venture in 1902 and making it as part of the data storage revolution. With this AI wave, we might be seeing similar stories in real time.
Most of the stuff they make industrially increases efficiency of downstream businesses in other supply chains and thus reduces environmental impact of making stuff like the phone you are using to comment (and the internet).
