Decorum.btc🥑

Lately I've been building a lot more with "infrastructure agents". When I joined AWS as a mobile dev, I was excited to learn how to build scalable cloud services. After a few years I was able to do a lot, but there was so much more to learn, and it becomes very complex and tedious. Frontier models are great at designing and provisioning what I'd consider complex infrastructure and tying it together with frontends. I started by creating test accounts with limited spend/scoped creds on AWS, and prompting creative things that I thought were challenging to get right. Agents are good at creating these interconnected multi-service cloud stacks. I've used the CLI and MCP, even signed in to AWS on a cloud agent browser and let the agent provision through the UI via computer use. And it's simple to spin them down (which used to be a challenge on it's own!). Because of this, not much tech debt because it's easy to fix and migrate as things evolve. Taking this beyond AWS of course this applies to other services like @convex, really anything.. You don't really need to even set up the API keys, just sign in to accounts via a cloud agent browser like @DevinAI, send a prompt, then close your computer. When the session is done everything is shipped, your environment variables are stored securly, you have a packaged up production ready app ready to go. And when you're ready to tear it all down it's also just a prompt away. It's such a new way of thinking for me. Most of my career this was so out of reach (or too time consuming) so my mind today still lives with these assumptions, I keep having to remind myself that "no, it really is this simple" (many such cases). Today I'm building three @EpicGames Unreal Engine games on an AWS fleet my agent provisioned, including Blender assets and GPU playtests 🤯. Devin created this diagram showing how it works: