Re:Highly classified US national security communications net...
by pokstad on Tuesday November 17, 2026 @01:38PM
(#50536089)
Or maybe it’s the enshitification from the AI slop movement. People who don’t understand the ramifications of their PRs making giant frequent changes to codebases while maintainers feel pressure to hit the approve button.
Re:Highly classified US national security communications net...
by gilfaethwy on Tuesday November 17, 2026 @01:49PM
(#50536283)
Let's not judge people submitting AI slop PRs too harshly. Maybe AI slop against open-source codebases, but a lot of the proprietary AI slop is a result of management directives and organizational pressures, not engineer desire to merge in crap code.
Re:Highly classified US national security communications net...
by vrganj on Tuesday November 17, 2026 @02:29PM
(#50536869)
> Maybe AI slop against open-source codebases, but a lot of the proprietary AI slop is a result of management directives and organizational pressures, not engineer desire to merge in crap code.
Then it is a failure of software dev individualism. There is a long-proven, battle-tested solution to management making unreasonable demands from labor: Unionization.
Re:Highly classified US national security communications net...
by btreesOfSpring on Tuesday November 17, 2026 @03:20PM
(#50537603)
This is another factor that all started with the twitter purchase and made its way into the fewer people is better movement in tech.
Re:Highly classified US national security communications net...
by insane_dreamer on Tuesday November 17, 2026 @01:51PM
(#50536321)
Nothing critical is dependent on Twitter (which has had plenty of hiccups), so what "worked" there doesn't "work" on critical systems
Re:Highly classified US national security communications net...
by btreesOfSpring on Tuesday November 17, 2026 @03:19PM
(#50537581)
That is the point of the post. It started with something very public and non-critical and has slowly made its way through the full pipeline into real systems our infrastructure relies upon. The consequences are finally showing. It is too bad most of the people who were raising the red flags were sacrificed to layoffs & dismissals.
Yeah, you can do fine with only one set of eyes on a problem. Yeah, it is more "efficient" in the short term. Culling lots of do-nothing people in your organization isn't going to produce many tears. Even so, devs and IT departments are now missing all sorts of backup and vital personnel that keep the gears oiled and running.