I wouldn't mind so much if they cheat on the way back but listen in earnest. There are use cases like teaching language where having the AI understand the sounds carefully matters a ton.
A potential sales tip: Going down the list of the $10 plan the first thing I saw was the 300 scripts limit and thought "no way". Pay attention to how supabase does it, basically no limits except compute and storage.
Technologies: Most recently Python and F#, SQL, .NET, Postgres, SQL Server, Typescript, Javascript, React, Ops with GCP, AWS, Azure, Further out: C++, PHP, EasyTrieve on OS/390 Mainframe if you go way back. I'm fairly knowledgable in functional programming and algorithms.
Roles: Interested in roles both Management and IC (if the problem domain is sufficiently interesting). Prior Successful Exit as CTO (350M, inflation adjusted 450M). Scaled eng orgs up to 80 people. Invented core IP at prior startups. Architected large scale systems.
I think the adoption hurdle will be hard unless you have a free plan that can be used for small things indefinitely. Having a hard cap on events would make me pass on this for fun side projects, which is where I would pivot later from to work projects. Just throwing that out there. This is why my last work project was supabase, I was using their free tier for some fun personal stuff.
If you have another vector for adoption that's fine too.
I understand. Honestly, it was never my intention to get rich with this project. Covering a bit of the development time, servers, and so on would already be nice. Since Genesis DB doesn't limit the number of instances you can run, I would have happily used it myself as a developer at that price point. I've thought about a one-time payment model before. But as I said, I do understand your perspective.
The flaw in this reasoning is AI can also help you understand code much more quickly than we could before. We are now in fractional bus factor territory.
I agree the risk of bus factor zero is reduced when ramp up time is reduced (through the use of AI enabled tooling), but I disagree in that you still have bus factor zero nonetheless.
Crisis management is a big part of the job, and the more people you have the higher the chance there is a crisis at any given point in time. Around 100 devs there's usually at least 1-2 things going on at any given time.
I feel like the whole distributing webasm binaries thing is tough to swallow. I get the argument, but surely there's a better way, like maybe you could make a tiny interpreter in webasm and distribute that with a human readable script.
