Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Poor James (Score 5, Insightful) 106

On the upswing, odds are pretty good that James will have a job in short order, helping to deal with the fallout of 'vibe coders' who don't know how to do real-world testing.

I'm already seeing bizarre corporate fallout from this - when a high value, highly paid individual "vibe codes" something that gets traction and then the executive team declares "now put it in production" and the legitimate questions are asked like "what are the requirements? how does it work? what are the dependencies? What are the SLAs supposed to be?" There are no answers, really. So then the slop has to be analyzed, almost reverse-engineered, and the execs get pissed because nobody knows the basic answers.

Even worse when asked "who will support it?" the answer is "well you will!" except that again, nobody knows how it works, and nobody wants to spend the time (read money) to figure it out. There's nearly never any documentation, and what documentation does exist is also slop and may or may not actually reflect the thing that was vibe coded.

So... yeah, the "AI" crash is going to, at some point, get very expensive on those who capitalized on the vibe coding trend, and very lucrative for people willing to clean up others shit. Vibe janitors, if you will.

Comment Re:Ok, so dumb question (Score 2) 159

Better. Almost all certificate renewals from a modern CA can be automated, old certificates get cycled out, new ones get cycled in. Apple's not actually the bad guy in this fight, in my opinion.

Also from my point of view, there's lower impact to the overall chain if an intermediate or root certificate is invalidated or worse, compromised, because while the number of issued certificates are higher, the process is more frequent.

I'd guess (but don't know) much of the pushback is from the older CAs that have not kept up with the times and are already losing ground to Let's Encrypt and the certificate managers run by cloud providers like AWS' Certificate Manager and Azure's App Service Certificates. It was the older CA's that originally pushed for a differential in the display of "extended verification" certificates, but nobody has really noticed that the "EV" portion has basically dropped out of the public view - which is fine, EV always seemed like a money grab to me by the CAs anyway.

Comment Re:Yeah, we need Debian (Score 1) 354

RHEL's lag times are fine by me. While I don't work with a giant-multinational corporation, enterprise stability is still of utmost priority to my staff and I. We like that while RHEL stays on top of security issues, they do not make frequent jumps to newer application releases without significant warning.

As far as RHN, if you don't like paying for support, use CentOS. We do for our development and testing environment, and can be assure that it will stay in sync, once the base platform port occurs.

For desktops, our devs use whatever makes them happy. I'm running Fedora 14 right now, and several others are using various debian-sourced releases.

I think the real detriment, as mentioned earlier, was the growing lack of diversity in the distribution sphere.

Slashdot Top Deals

Work expands to fill the time available. -- Cyril Northcote Parkinson, "The Economist", 1955

Working...