this post was submitted on 21 Jul 2025
13 points (100.0% liked)

Technology

39739 readers
150 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago
MODERATORS
top 3 comments
sorted by: hot top controversial new old
[–] thebardingreen@lemmy.starlightkel.xyz 12 points 6 days ago* (last edited 6 days ago) (1 children)

I'm working with a team where my business partner and I are external consultants, but they also have internal developers (who are mostly very junior and need hand holding with things like using git).

Anyway, the CEO (without talking to us first) hired a pure vibe coder with no software engineering experience to build the user interface. Super nice guy, super easy to work worth, super eager to learn but OH MY GOD THIS CODE.

A lot of my work is / has been in cybersecurity (mostly for the space industry / NASA adjacent projects, but also less recently for start ups and fortune 500 companies). This app is the worst I've ever seen. The AI writes things SO weirdly. 30k lines of typescript to do something we could have done in 6k. Reams of dead code. Procedural code to do repeatable tasks instead of functions / classes (10 different ways of doing the same thing). API keys / data base credentials committed to git. API Keys stored in .env but then ALSO just hardcoded into the actual API calls.

AND no. At the end of the day, it wasn't cheaper or faster than it would have been to hire us to do it right. And the tech debt now accumulated to secure / maintain this thing? Security is a long term requirement, we're bringing a buddy of mine in to pentest this thing next week, I expect him to find like 10-12 critical vulns. Wow.

tl;dr: If a project requires security, stability, auditability, or the need to quickly understand how something works / why something happens, DON'T vibe code it. You won't save money OR time in the long run. If you're project DOESN'T need any of those things (and never will), then by all means I guess, knock yourself out.

[–] bl4kers@beehaw.org 1 points 6 days ago

I haven't heard discussion on this topic, but isn't it possible for the LLM to interpret that 30k as good, reinforcing its own bad habits?

[–] altphoto@lemmy.today 1 points 6 days ago

Is was us who scorched the sky right?