Firstly, you talk about locking developers into a workflow. While I accept linter warning exist, in the real world you must make them earnings-as-errors or they are ignored and become just yellow noise.

But you then go on to formalise like below. There's no ambiguity there. No room for manoeuvre, no nuance. The whole post doesn't read like an aim, it reads like a formalised rule. You talk about locking programmers in. That's not the real world I've been in.

I'm not saying that healthcare data exchange standards are a worry but also this:

Amazon's help LLM "Q" can be useful but sometimes it hallucinates features that sound reasonable but don't exist, like "add instance to existing cluster" on a headless cluster.

The replies *did* have a solution that worked. 1/2

#aws #devops #llm #ai

And a Moth is a beautiful aircraft to fly too. My Dad and I built balsa aircraft from plans when I was a kid. The balsa wasn't cut for you, you had to delicately cut out the ribs from the paper plan and pin them to flat balsa sheet. Here he is with a Pitts special mid-80s.

Ah! Typography only!

Pop Will Eat Itself - This The Day, This Is The Hour, This Is This. 1989. Artwork by the Designer's Republic.

We get the business/client side to choose the order. Like Bartlett in The West Wing, it's always "What's Next".

My face isn't a real face. Something of an insult.

Missed opportunity for #AWS to have a sense of humour.

This is "achievement unlocked" like the time I corrected Jon Skeet on S-O.

Whenever I see a band line-up without a drummer:

TFW you've exhausted all the swear words you know at #AWS #CodePipeline and you then see this. 😊

Do I keep going and possibly break something or do the next bit Monday? 🤔

AWS #devops be like: