Holy cow, I'm actually quoted in The Register!
They did a short little phone interview with me last night, so I guess I'm like famous now? ;-)
https://t.co/ihoZ3fZtw2
Anyways, I told him to break his changes into individual pull requests and I'll consider them individually.
He started, but so far he's not passing CI, so CI is doing its job 😆
Person wandered into one of my projects with a complete rewrite in tow, completely breaking the public interface.
Then he started wandering into open issues commenting that his changes will fix all of these problems.
That's just... not how... we do things... My dude
I don't think it's AI slop. It doesn't have the stink.
I think he's just an over eager kid… or old person? One of his changes is phpBB support… which I don't know anyone under 50 to use.
GitHub Actions single core performance is surprisingly bad.
I built a benchmark for one of my tools that runs on every PR like this…
These benchmarks take 6 seconds on my local machine, but 40 seconds on GitHub
Oh dang. Pitchfork gave Tricky's Blowback a 3.1 / 10 back in 2001... and the review is so mean spirited...
https://t.co/W4n1l4WEiG
It's one of my all time favorite albums and I would argue one of the best of the late 90s/early 2000s
@iansltx For what it's worth, it actually seems to do a better job of it than Claude for whatever reason.
It's pretty decent at finding problems in complex interactions particularly at the seams.
@blbraner Package managers like npm where what is on GitHub isn't guaranteed to be what you download make the problem so much worse.
Composer and go mod got that part right at least
Every CVE that boils down to "if you let the end user specify a regex, they can cause infinite backtracking" should be tossed out with the note "don't do that"
New CVE: Arbitrary code execution when letting end-users execute arbitrary code