Solid first SaaS. Shipping something at 16 that solves a real infra pain point is no joke.
WebSocket management is one of those things that sounds simple until you're dealing with connection state, reconnects, and scaling across edge locations. The ephemeral session idea is smart for use cases like temp chat rooms or live event channels where you genuinely don't want messages persisted.
Few questions from a practical standpoint: what happens when a session hits connection limits? And what's the edge infra under the hood, Cloudflare Workers/Durable Objects? That'd be worth mentioning on the landing page since devs evaluating this will want to know what they're building on top of.
Also, since Google auth is broken, Might want to throw a banner on the signup page so people don't bounce thinking the whole thing is down.
Keep shipping. Most devs twice your age are still "planning" their first project.
Seeing a version of this from India. Every decent ML engineer is getting vacuumed into foundation model work or infra roles at hyperscalers. Teams building the actual application layer are struggling to hire.
The stat about OpenAI needing 20% of the existing skilled trades workforce for their data centers is nuts. That's not a scaling challenge, that's a resource extraction problem.
Anyone else noticing this hitting developer tooling and devrel budgets too? Everything that isn't "AI infra" is getting squeezed hard.
simonw nailed it. The pain was never "writing code." It was the random hour lost debugging why CI broke overnight because some dependency shipped a breaking change.
I run a dev community of ~1500 devs. The ones getting the most out of agents aren't throwing away frameworks. They're offloading the stuff nobody enjoys. OAuth scope spelunking, boilerplate migrations, flaky test debugging. That's where agents shine.
The actual risk nobody talks about: if you've never manually debugged a race condition, you won't catch it when the agent introduces one. Agents amplify what you already know. They don't replace knowing things.
The multi-model approach makes sense. We've noticed different models handle different things better, so being able to run them side by side is pretty useful.
The dynamic workflow stuff is neat. Most tools are too rigid once you start. Will be interesting to see how it handles unexpected turns.
WebSocket management is one of those things that sounds simple until you're dealing with connection state, reconnects, and scaling across edge locations. The ephemeral session idea is smart for use cases like temp chat rooms or live event channels where you genuinely don't want messages persisted.
Few questions from a practical standpoint: what happens when a session hits connection limits? And what's the edge infra under the hood, Cloudflare Workers/Durable Objects? That'd be worth mentioning on the landing page since devs evaluating this will want to know what they're building on top of.
Also, since Google auth is broken, Might want to throw a banner on the signup page so people don't bounce thinking the whole thing is down.
Keep shipping. Most devs twice your age are still "planning" their first project.