zackliscio

Sorry to hear about the customer churn, but the MCP-first strategy makes sense to me and seems like it could be really powerful. I also suspect that the bring your own agent future will be really exciting, and I've been surprised we haven't seen more of it play out already.

Agree there will be a place for no-code and low-code interfaces, but I do think it's an open question where the value capture will be--as SaaS vendors, or by the LLM providers themselves.

It would probably have been more accurate to say "the cost of writing code" -- and you're totally right about the rise of other duties (and technologies) that expand to fill that gap.

As a dev team, we've been exploring how we grapple with the cultural and workflow changes that arise as these tools improve--it's definitely an ongoing and constantly evolving conversation.

This is a good example, but the build vs buy decision in this case also includes viable open source options, which become even more attractive when LLMs reduce the implementation + maintenance barriers.

Great point, and I agree the catch-all nature of the category feels overly broad. At our company, we've felt this shift most clearly on the app-building side so far but I'm curious to see how the low-code data applications fare as context windows grow and the core LLM providers improve their collaboration tools, governance, and improve the UX of on demand app creation. And nice to see you, too!

thanks for flagging! reached out the HN team to update -- can't delete or edit once there are comments.

The rails metaphor is especially weak here. The author's argument conflates the idea of rejecting an established field of knowledge outright with Altman's critique of the absolute way in which some ideas have become taboo in society.

Nice work, this is an awesome tool. As a founder would love to be able to share it with my co-founders--any account sharing on the horizon?