So, there is professional skills and then there is "soft skills" which at many places is a euphemism for political theatre. Nearly everyone I've ever met has professional skills; few can stomach "soft skills"
If anyone was around for the dot-com bubble any company internet related or with a web like name was irrationally funded, P/E didn't matter, burn didn't matter, product didn't matter.
AI has all the same markers of a the dot com bubble and eventually venture capital will dry up and many AI companies will go bust with a few remaining that make something useful with an unmet niche.
Proper CI/CD for Gitops is actually really hard, how do you alert to failures that doesn't tie you to a specific provider and follows an alert chain? How do you chain dependent Gitops pipelines without coding a giant pipeline mess? How do you do healthchecks in a portable manner on what is deployed without giving the CI/CD runners basically global root?.. and on and on and on, this is all solved by Fluxcd or Argocd.
The whole business model of cloud providers is to charge a premium for their ecosystem and to create lock-in by making everything interdependent. A Kubernetes deployment could cost 100k/yr a similar cloud deployment would be ~1m/yr.
Have you worked at an organization without RFCs, ADRs, etc? The alternative is really just the wild west and whatever politics or pull a person has. RFCs and ADRs are good in the sense that they document _something_ even if the document is junk it's better than an assumption.
Really though it's the organization (and people) that makes or breaks anything.
It's strange organizations want to push users off of a minor $100/yr/user cost when there are many other ways to save money that don't involve making a power user useless for years.
I just want prettier default diagrams in d2, the default theme (and other ones) is a hard sell to orgs where management isn't technical. Something similar to the Obsidian diagram theme
I recently looked into this at it looks like the IETF(?) RFC draft for SSH3 was abandoned? It's great this exists but I think the standard needs to be done as well.
Ubiquiti hardware is an great but their software has some of the worst QA I've seen in my life, the forum is basically an continuously ignored issue tracker where I've found dozens of problems I'm having with no solutions (about 200 aps and 150 switches/routers). Ubiquiti software is absolutely abysmal.
2. Why do you think current programming paradigms are bad?
3. What changes to current operating systems need to happen?
[2] My view is you want to pass terse but informative information to a compiler in order for optimizations to take effect and there are three roads programming languages take: abstract away by layering which burdens the programmer to unravel everything (C++), abstract away from the hardware so much that specifics are hidden (most high level languages) or something similar to C.