pull down to refresh
I see the lack of accountability and slop avalanche as a product of our evaluation bottleneck. Truly think that's the problem that needs to be solved: our ability to actually process the flood of unlimited AI generation we're facing.
I see what you mean about content discovery.
I agree with that. I think that "AI will take your job" made a lot of people overconfident. Also "I don't read, I ship" in January was a terrible example. But I can see a lot of devs liking that because now you don't have to review deeply, or think. Which is the only thing you should be doing. And it's the least fun part!
To some degree, we can fight fire with fire. But you cannot let an LLM be a judge. You cannot ask it: "is this ok?" What you can ask is: "find all the problems." And then you have to read it to make sure that those really are problems. Currently, hit rate is... 90% or so, so I don't use it for critical things because a 10% error rate compounds rapidly, also when these are false positives.
And I see the difference
I think I even see the difference in the bugs:
This is clearly an LLM bug, right? I don't think a human would write code that could cause a bug like this. It's a funny one, but I don't think it was intentional. It makes me wonder about the rest of the code, though.
/cc @k00b
Nah, here's an LLM bug: https://github.com/postcss/postcss/pull/2119/changes/22cb61b7e893a4ffe762e62d830808b6bddd956e - see it?
I spotted it in the diff when I was doing dep upgrades: #3189 but I misclassified the impact and I didn't see the problem during testing because I didn't test multi-paragraph posts: So after merge, @SimpleStacker found it in the live env: #1556331
So that's on me being not precise enough in testing and misinterpreting the sass integration, double-whammy opti-fuckup.
the rest of the code
In general, SN 1st party code is carefully engineered, more than what I can dry-eyed say about what I'm seeing in the npm ecosystem in general lately, including some of the SN deps. I spend a lot of time validating if there is impact to new bugs introduced in bugfixes. Luckily, most of the time, like for example some of the shit npmsec puked out last night that then contains new bugs in a dotdot release, is pre-empted by measures taken in the code / config to disable some nextjs features that no one should ever use to begin with, and thus safe.
But, sometimes it's pretty complex, and fuckups, like mine, can happen.
It's intentional. I thought it was cute.
It makes me wonder about the rest of the code, though.
lol
I just see a lot of code, and in the past 4-5 months, I see an overwhelming majority of slop code. And I see the difference. Because the code doesn't carry accountability anymore, because the thing that wrote it isn't sentient and has nothing at stake, and the person it wrote it for can just blame anything on the AI, because even labs get away with that. ZERO accountability. Code with no soul may as well just have been a prompt that got shared. At least the prompt had a bit of soul.
As for content discovery (and then I don't mean research, but the SN kind), what I have really come to appreciate, and moreso since about a year, is the human interest that triggers a post. You see, I'm not interest in any content that exists, I'm interested in content that triggered you, or other stackers. And if I run into something that triggers me, I'll share it too.