this post was submitted on 07 Aug 2026
1293 points (98.9% liked)
Microblog Memes
11973 readers
2317 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
- Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
- Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
- You are encouraged to provide a link back to the source of your screen capture in the body of your post.
- Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
- Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
- Absolutely no NSFL content.
- Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
- No advertising, brand promotion, or guerrilla marketing.
RELATED COMMUNITIES:
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My experience is that prepping a code review with LLM is a safer bet than having a person review LLM code. None of this should replace static analysis or human code review, but it can provide a rapid feedback about something that looks off either to the original developer or helping a reviewer catch a detail that might have escaped their attention span. LLM missteps don't matter so much, since the audience is a human (an exceedingly high false positive rate is annoying, but not a disastor). Also why it makes for a handy facility for security, mistakes don't matter, missing something is no worse than before, false positives can be ignored.
If your scenario is well served by TDD with absoutely comprehensive test cases that can grade with absolute perfect coverage of all the scenarios, then code gen can thrash on that and make progress, though it's a bit token heavy because there's a fair amount of guesses and reguessing. But if you AI gen the tests and the code, then you might get into weird states. Even if you didn't mean to have the AI mess with the tests things can go south. A couple weeks back I tried to prompt up a change that I thought should have been reasonably within the capabilities of the model, along the way it failed a long standing test and fixed it by changing the test, making the determination that the test case needed correcting to let it pass, instead of trying to pass the test case. The test case was, in fact, correct, it screwed up.
Part of the problem is 'writing code' is about as diverse as 'writing text', and some folks are working in territory that the LLMs can chew through competently and others are places where the LLMs struggle, and then there's the person lulled into a sense of security by being in the former category until one day suddenly they are in the latter unexpectedly for no apparent reason.