nwmcsween

This is like string functions, there are some variants with just crazy SIMD when the mean string length is ~14-20 bytes

Junior and mid-level engineers will now require more senior engineers to sign off any AI-assisted changes, Treadwell added.

Beatings will continue until senior engineers leave?

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.

Use helm to generate the manifests with a Makefile, use Kustomize to change said manifests for prod, staging, etc.

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.

This would be my personal hell, let me just read n files of AI slop from the CEO.

What I don't understand is why not use what I've seen in industrial processes? Why not a low boiling point liquid and a heat exchanger? Or even better power a turbine like biogas plants do

It's because of their target, they target corporate non-technical IT where the end users have no idea of what they actually want but want it all integrated, badly, and it all works brilliantly for Microsoft as feature x is $y/mo.

This is more than enough to prop them up. More often then not the consultee already has a plan even if the plan is horrendous the consulting company is there to insulate management from any fallout (read incompetence).

Sadly the time when an org wanted people to excel and really grow at is over, the new normal is peak capitalism of maximizing value.

People develop relationships with coworkers, you care if someone has issues, you're happy if a solution makes customers/coworkers happy but none of that matters to the lawnmower, it just mows lawns.

Sam Altman complaining about "unethical" corporate behavior is pure gold

Why "Remember"? php-fpm is probably powering millions of sites right now.

I have first hand knowledge with large consultant companies, they are largely sales teams with minimal IT knowledge. I had to help a one of their overseas "senior cloud professional" that had issues even understanding how to navigate the cloud UI.

Just use `open_file_cache`?

The goal of an abstraction should be to make reasoning about the code easier, generally that means hiding complexity but that shouldn't be the goal.

In my opinion a common issue in programming is premature abstraction without understanding the interactions as a whole.

I mean considering I did document classification back in 2010 using tesseract, I wouldn't say it was impossible.

S6 and really all skarnet code is kind of "djb c" which makes reasoning about it a bit convoluted.

DSC has a really really wide variety of windows modules and unfortunately there isn't really anything comparable, Puppet and Ansible do have interfaces to DSC modules but it's kind of janky compared to just using DSC.

I mean making changes in prod without testing will do that, Gitops or not.

Canada has very lax crime punishment, which is sad for the victims. There's been cases where people have killed others after 3-x crimes and released with future court dates.

So HAProxy has a bit of a love/hate relationship in Kubernetes, the problem really being UDP and the mess(?) that is proxying stateless traffic. The Gateway API kind of expecting UDP proxying support doesn't help.

100%, technology evolves, sometimes to a dead end but it keeps moving and it's an interesting, frustrating and fun ride.

I expect this to rise dramatically in Canada, Canadian tech salaries are a race to the bottom due to companies exploiting students for PR where they can advertise barely livable wages for something in the states that would get $150-250k.

If you look at COL and pay Vancouver regularly offers 40-60k CAD salary ($29k USD) where rent for a bedroom is $1.5-2k/mo

Can this be renamed "setenv() is not webscale"?