Enterprise tooling (aka a usable API) and it stays out if my way.
rolaulten
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 almost never interact with desktop Linux. That's a horrifying trend.
With how they keep shoving snaps at everyone? At my work a migration to Debian is starting to be openly pondered.
Important question: Pulumi or Terraform?
I have a framework. Hands down the best laptop I've ever worked with/on.
It's not uncommon for the password manager to not be on the same system as where the password is being entered - hence a human needs to type. For example: consumer electronics with their own dinky little screens. Smart TVs/game systems and servers where remote access is not possible (or copy/paste does not work by design).
As an ops person I disagree! Our arbitrary changes are documented in a jira ticket in the ops project. If you can't view the ops project fill free to open a ticket in ops and we will triage it when we feel like it.
That's the scary thing. It looks like this narrowly missed getting into Debian and RH. Downstream downstream that is... everything.