IMO nobody was paying for magic compute. they're paying to not touch ten years of glue.

if agents eat that glue, the moat gets thin fast.

> agents eat that glue

No wonder they hallucinate :)

	▲	andyhedges 4 hours ago \| parent [-]
		It's when they sniff the glue, then things get wild.

▲

drewnick 2 hours ago | parent | prev | next [-]

The problem is a lot of this glue is proprietary by design at the various cloud services. I realize there are open source and alternative abstractions for a lot of of the same services, but there’s still quite a bit of glue if you’re on AWS, for example, and looking to move to bare metal.

But maybe I’m just thinking of the current capabilities of agents, and if we fast forward a couple years, even removing these abstractions or migrating will be very low friction.

	▲	reillyse 2 hours ago \| parent [-]
		But you can run most of the glue on your own dedicated instances. I run k8s on a bunch of dedicated servers that are super cheap and I have all bells and whistles - just tell your coding agent to do it. You can literally design the thing you would never do yourself and it works brilliantly. Postgres running on dedicated hardware replicated and with wal backups - easy just tell codebuff (my harness of choice) to do it. Then any number of firewalls, load balancers, bastion servers, etc. if you can imagine it , codebuff will implement it.

▲

zamadatix 5 hours ago | parent | prev [-]

Yeah, at the last job there was a single outdated external wiki server left sitting in DO for those kinds of reasons while everything updated and internal had moved already (if not twice). If it hadn't become such a security risk it would never have been moved.