this post was submitted on 22 Jan 2026
81 points (100.0% liked)
technology
24197 readers
296 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A friend who joined a programming school told me they scrapped the entire curriculum some months into the course and started teaching vibe coding instead.
What's sad is that vibe coding is basically only valuable to people who have experience and know what they're doing. If you're teaching it in school, you're teaching nothing.
It's the equivalent of teaching the power rule of derivatives in a calculus class, then saying "that's what a derivative is" and not explaining the underlying proofs.
Yeah the idea that vibe coding is much of a skill is mostly a scam to obscure the capabilities and limitations of LLMs.
I'm still under the impression that it's totally useless. I've written much better and actually more code since I stopped using LLMs (I had co-pilot for a bit).
I really do think that people have been fooling themselves with AI slop. It's really easy to feel like you're doing a lot when it's just constantly spitting stuff out on the screen.
I'm recently going back and re-writing a package that I used AI to help write like a year and a half ago. This is the one that made me abandon AI, since it just continued to fuck up patterns in ways that were incredibly difficult to fix. Then the package suddenly got a decent amount of users and I was locked in.
I came up with the high level concept and used AI to help scaffold and boilerplate out models and stuff from a spec, which should have been a sign that I was doing something wrong.
Now I'm rewriting the whole thing from scratch, and one of the big things I've noticed is that the types of things I'd use AI for before, I'm now writing build scripts for. Which makes maintaining the library like 10x easier. It also forces me to distil the library backend down into the simplest possible form to keep the buildscripts simple.
I'm also forced to be way stricter with my typing solution (Python) since I can't just offload "make this right" to the AI and actually need to use strict static checks to keep the layers properly synced. AI Python tends to be awful when it comes to type hinting if it even does it.
Oh it's great at generating verbose near infeasible for humans to maintain code bases. I think the asbestos analogy is pretty on point.