IT JUST GOT INTERESTING!!! As a person who didn't find a model I liked past Opus 4.6 (except GPT Terra...) Now I have my choice :D

@housecor I didn’t realise you moonlight??

TL;DR: If the workload can be handled well by Opus 4.6, it has a substantial cost advantage. Fable 5.1 needs to produce meaningfully better results, require fewer retries/agent steps, or make heavy use of cached context to justify its 100% premium on input and output tokens.

You are so correct here! I've actually managed to do a bunch of good in this flow that ends up with an output to create an attestation as follows and it's working well

If you require me to login to Calendly using X and it has these permissions, then that's a BIG no from my side:

I've spent the last two months talking about building the machine that builds the machine. The idea isn't complicated: stop treating AI as a better interface for humans to do work, and start building systems that can create, modify, operate, and improve other systems. For infrastructure, that means the goal isn't an AI that writes Terraform faster. It's a system that can understand infrastructure, reason about it, change it safely, and get better at doing that every time it runs. Last week at Microsoft Build, @steipete gave a talk called "Build the Thing That Builds the Thing." - lnkd.in/eGPE3VUZ That title stood out because it describes exactly how I think about AI. Most people spend their time prompting agents. I spend my time building the systems around the agents. The goal isn't to become better at prompting. The goal is to build a machine that can reliably produce outcomes, improve itself, and do more of the work without requiring constant human intervention. We're not heading toward a world where humans sit in front of chat windows all day. We're heading toward a world where we build machines that build machines. The biggest opportunity isn't replacing individual tasks. It's creating systems that continuously generate, operate, and improve the next layer of systems above them. That's what I've been writing about throughout this blog series (stack72.dev/the-lifecycle-of…), and it's what we've been building at swamp-club.com for months already. It feels like the industry is finally converging on the same idea and I am excited about it!

Looks cool eh ;)

This is the very basics of what I needed to create an EKS cluster with @thesysteminit Next up... Fargate Profile!

First things that's AWESOME! Real time look up of the currently supported Kubernetes versions in EKS:

ok, so I have separated our location so that I can validate that your credentials has access to it - then you can connect it to whatever resources you want