this post was submitted on 07 Jul 2025
1219 points (100.0% liked)
Technology
72788 readers
2759 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Vibe coding is 5% asking for code and 95% cleaning up the code, turns out replacing people with AI is exactly the same.
Jup. But the same goes for developers that go way too fast when setting up a project or library. 2-3 months in and everything is a mess. Weird function names, all one letter vars, no inversion of control, hardcoded things etc. Good luck fixing it.
This is what I fight against every goddamn day, and I get yelled at for fighting against it, but I’m not going to stop. I want to build shit that I can largely forget about (because, you know, it’s reliable and logically extensible and maintainable) after it gets to a mature state, and I’m not shy about making that known. This has led to more than a few significant conflicts over the course of my career. It has also led to me saying “I fucking told you so” more than a few times.
I have had several situations where I didn't even have to give knowing looks, everybody in the room knew I told them so six months ago and here it is. When that led to problems working with my leadership in the future (which happened more often than not), that was a 100% reliable sign that I would be happier and more successful elsewhere.
Stack Exchange coding is 5% finding solutions to try and 95% copy-pasting those solutions into your project, discovering why they don't work for you, and trying the next solution on the search list.
I'm still not sure how this is any different than when I used stack exchange for exactly the same thing.
Well, SE code usually compiled and did what it said. I guess that part is different.
Practically negligible then...
However how the heck have you all been using stack exchange? My questions are typically something along the lines of:
"How to use a numpy mask with pandas dataframes"
Not something that gives me 50 lines of code.
Oh, yeah. But I assumed that's how competent coders use chatgpt. For edge cases and boilerplate.