points by mikepurvis 2 days ago | 0 comments
On some level, yes, though when I choose a saas product, what I'm really choosing is not a basket of features, but rather someone else to be worrying about scaling, monitoring, security patches, uptime, etc.
Like in theory your agents can build all that too, but all the ancillary bits benefit a lot from being spread across a pool of users with different time zones, release cycles, whatever.
[–] jopsen 2 days ago
[–] francisofascii 2 days ago
So I wonder if the more generic SAAS platforms (like Azure, AWS) that can offer scaling, monitoring, security patches, etc. will start to niche or industry specific Saas tools. Since the "basket of features" is not what is really needed.
[–] gadders 2 days ago
Yeah, and admittedly you need to pick your problem domain sensibly.
i.e. you wouldn't vibe code your general ledger, but I'd guess Confluence is pretty vulnerable.
And its the same reason you'd rather have a SaaS vendor, than asking an agent why the cloud bill keeps climbing and then have to debate the impact of delete such and such VMs or databases that nobody knows what do :)
You also don't ask your agent to start from assembly.
Things you can get upfront as libraries or services are things you and your agent don't have to worry about.
I'm not even sure there is anything new here, just that we have a capability jump with LLMs, you'll probably prefer spending it on building features, not replacing vendors (unless they are crazy expensive).