Just to give an outsider perspective to anyone reading this. I live in the Seattle Metro, have worked for Microsoft, and now work at a unicorn. I have a list of skill and experience that any ops department would drool over. Amazon is is one of the companies I won't even apply to unless I'm desperate for a job (and even then I'm not planning to stay).
And I know I'm not the only one.
How can you not link the rpgnet review of such a...system. https://www.rpg.net/reviews/archive/14/14567.phtml
Odds are you have met someone with it, but the eye color shifts depending on what colors are around them.
Which veggie dog worked for you? I can't find one that grills correctly.
When I was taught it it was not pure left/right. Rather a method to differentiate levels of Libertarianism form other branches of liberalism focused on social justice (rising tide and all that). Any idea where you read it? Poli sci wonk phrasing being included into more popular literature is always fun to see.
Enterprise tooling (aka a usable API) and it stays out if my way.
Along a similar vain to making a git friend, buy your sysadmins/ops people a box of doughnuts once in a while. They (generally) all code and will have some knowledge of what you are working on.
Let's be clear - current AI models are being used by poor leadership to remove bad developers (good ones don't tend to stick around). This however does place some pressure on the greater tech job market (but I'd argue no different then any other downturn we have all lived through).
That said, until the issues with being confidently incorrect are resolved (and I bet people a lot smarter then me are tackling the problem) it's nothing better then a suped up IDE. Now if you have a public resources you can point me to that can look at a meta repo full of dozens of tools and help me convert the python scripts that are wrappers of wrappers( and so on) into something sane I'm all ears.
I highly doubt we will ever get to the point where you don't need to understand how an algorithm works - and for that you need to understand core concepts like recursion and loops. As humans brains are designed for pattern recognition - that means writing a program to solve a sodoku puzzle.
There is more to a program then writing logic. Good engineers are people who understand how to interpret problems and translate the inherent lack of logic in natural language into something that machines are able to understand (or vice versa).
The models out there right now can truly accelerate the speed of that translation - but translation will still be needed.
An anecdote for an anecdote. Part of my job is maintaining a set of EKS clusters where downtime is... undesirable (five nines...). I actively use chatgpt and copilot when adjusting the code that describes the clusters - however these tools are not able to understand and explain impacts of things like upgrading the control plane. For that you need a human who can interpret the needs/hopes/desires/etc of the stakeholders.
That's more or less it.
For example, I've got somewhere around 700 users. If we don't have SSO (SAML preferred, oauth as a fall back, and good whiskey is required for ldap/ad) whatever your attempting to buy won't pass review. Now Timmy the sales drone knows that, and so does their leadership - hence the SSO tax.
I use it a fair bit. Mind, it's something like formating a giant json stdout into something I want to read...
I also do find it's useful for sketching out an outline In pseudo code.