Earlier quoted context omitted.
I think this policy is probably more prescriptive than I would go with myself. I like to think of my risk tolerance first to help make that determination. For example, I use a vibecoded internal tool written in Go. I don’t even know how to write Go. Haven’t read a single line of the code. I just wanted to move from bash scripts to using cloud SDKs for performance reasons. But the internal tool is a convenience tool,…
> I just wanted to move from bash scripts to using cloud SDKs for performance reasons. What is this supposed to mean? How is a “cloud sdk” more performant than a shell script?
There’s a bit less waiting around.