109
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Aug 2026
109 points (100.0% liked)
Lemmy Shitpost
41313 readers
2442 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 3 years ago
MODERATORS
"this looks vibe coded" doesn't mean "we don't like your project because it used ai"
it means "your project for fucking sure does not do what you think it does because you are not a skilled developer enough to understand the code that the AI generated for you"
to which the counterargument the slopper would throw is "I wrote tests for requirements and the tests are passing"
how would a slipper know the code generated fits the requirements vs strictly only passes test cases ?
This is a helpful clarification, thanks. Then my question to you is, should the viber cease and desist? Is this not a valid way for them to foment an interest in software/tool/website development? Surely if their code has deep issues, they'll discover that eventually and maybe learn from it, right?
Like, someone could try to learn a language by only using an ai translator. It's lazy and not as effective, but I wouldn't discourage someone from pursuing the language on account of that.
I am Java developer, and I don't understand how exactly JVM works, for example. I'm not sure, how much my app will consume memory and CPU resources. I don't know when garbage collector will do their work. I even don't know what JIT and AOT compilation. And this doesn't prevent me from doing good, effective and useful things. May be they are not the best. Maybe writing them on C or assembler will be more optimized and effective. But anyway, I am OK with that and trying to accept vibe coding same way, as I accept myself and my job.
Difference is that vibe coding doesn't create 20% more CPU usage or 30% more RAM usage because it doesn't understand the underlying mechanics (or, it could but that is not the important part). LLMs will happily provide you with solutions that consists of plain text password storage, leaking personal information through open APIs, and business crushing vulnerabilities. A sharp developer should be able to catch that, but if you're reviewing 5000+ line PRs daily that's been spat out by LLMs it'll be impossible to catch all failures. And for someone who doesn't know all those nonfunctional requirements that a business absolutely must have it'll become a nightmare for the receiver of the code.
So to be clear: For functional requirements LLMs are a bit better but still needs hand holding. For nonfunctional requirements they're dog shit as that's the part that more often than not has to explicitly be mentioned. And being able to identify nonfunctional requirements and when they're not met is the difference between a junior dev and a 10+ year lead.
Slow app? Just add resources. Vulnerable app? Actual compliance and business risk.