The thing about people talking about building with AI is that they always talk about how they’re building, what tools they use, and how much they use them. Much less is said about what they actually built, or what impact it had. The tool becomes the job. And the purpose.

i don't want the latest and greatest. i want stability.

After doing it manually for the last 10 years I finally had enough. Customers can transfer ownership to somebody else within the app! That's why you should let programmers do customer support 😅

I think it's becoming really, really important that with @outseta you can pick up your entire business... Payments, auth, CRM, emails, your support history... And rebuild your business on whatever tech you want, anytime. How we build is changing fast. Outseta makes you agile.

When I built menugen ~1 year ago, I observed that the hardest part by far was not the code itself, it was the plethora of services you have to assemble like IKEA furniture to make it real, the DevOps: services, payments, auth, database, security, domain names, etc... I am really looking forward to a day where I could simply tell my agent: "build menugen" (referencing the post) and it would just work. The whole thing up to the deployed web page. The agent would have to browse a number of services, read the docs, get all the api keys, make everything work, debug it in dev, and deploy to prod. This is the actually hard part, not the code itself. Or rather, the better way to think about it is that the entire DevOps lifecycle has to become code, in addition to the necessary sensors/actuators of the CLIs/APIs with agent-native ergonomics. And there should be no need to visit web pages, click buttons, or anything like that for the human. It's easy to state, it's now just barely technically possible and expected to work maybe, but it definitely requires from-scratch re-design, work and thought. Very exciting direction!