131–140 of 158 posts
Earlier quoted context omitted.
Same promise all the no-code or low-code app builders claim. Anyone who has done a serious project with LLM help knows it is no where near able to do half the things needed to run a project.
Right now, sure. But when a 21 year old is picking a field they need to think 10 years from now.
> i’m breaking up with vibe coding. here’s why. I eventually figured out Andrej defined the term seriously, but initially I thought "vibe coding" was a parody. As in, it's was ridiculing people who can't code and won't put the effort and just kind of like letting the LLM drive. A bit of a https://en.wikipedia.org/wiki/Poe's_law in action I guess.
Earlier quoted context omitted.
I don't dislike it but I don't love the lack of capitalization. Not really sure why that trend is on the uptick.
Zoomers that write in lowercase because it's more "chill"; go figure. It's a pretty reliable indicator that you're talking to someone < 25 years old.
Funny how it's coming back, with the younger generation embracing it. Everything cycles, I guess.
Well... sorta. If you're working on a personal project or open source project, then sure, yes, absolutely. If you're doing coursework or have explicitly set out to learn something new, then sure, yes, absolutely.
But when you're working at a job, they want you to use whatever tools will get the work done the fastest, and they usually don't care all that much about quality[0]. They don't care about your journey or process. They just care about the final product, and whether or not you met their arbitrary deadline.
[0] In my experience, the vast majority of "quality initiatives" at software companies are about fixing existing stuff that's broken, not about putting processes in place to ensure quality for new stuff. Even when the latter does happen, inevitably those processes will be short-circuited when there's a tight deadline.
Earlier quoted context omitted.
What is coding without critical thinking? I never vibe coded, and I don't understand this trend AT ALL. I read how copilot and such are detrimental to critical thinking, and I am even consciously scaling back on copilot use now whenever possible, and prioritizing Google search, reading documentation, blog posts and stackoverflow now.
Vibe coding hasn't really hampered my critical thinking. It just means I get ideas into practice faster, and it means that for new concepts I can get to itterating much faster. Perhaps I have the concept wrong, because half the time I'm still editing code by hand.
Using AI to assist in locating the right library function or similar to documentation has been effective to speed up my development, but I really dislike using it to autocomplete whole functions or large swathes of code, because then I have to spend time reading and understanding code I didn't write. This doesn't ultimately feel "faster" when I own what I write.
(Obviously, this post is tongue-in-cheek, but I'm making a real point - almost all code we use is code we didn't write. I don't think that's what differentiates Vibe coding code.)
Earlier quoted context omitted.
No, with vibe coding you are not a reviewer an editor or an author, quoting from the source: There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. ... I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.
Odd. How can one get the vibes without looking at the code? Like gleaming diamond vibes versus confused spaghetti vibes.
One problem I have is that AI is writing code I don't understand completely, yet I'm still responsible for it. Vibe coding seems like an echo from the future.
I find that even though I have to spend time understanding what the llm wrote, it's still faster and less energy sapping than if i write the code myself. Plus I just get the LLM to write tests for it's code and I make sure the coverage is complete. But it does make me feel uneasy still, like a dirty little cheat.
Earlier quoted context omitted.
> Vibe coding is here to stay. I would say this is true in the same way that copy-paste coding functioned and that vibe coding isn't fundamentally different. It can be a useful approach to a variety of problems. Having capable, knowledgable, and skilled employees is important to businesses though. If your business is something easily approachable then you are at risk of being outcompeted from companies with more skil…
I'm not convinced the two are necessarily mutually exclusive. Surely a skilled developer could make use of AI to produce stuff faster, while still understanding everything and making sure the code is well written (well generated?) Haven't really tried vibe coding myself yet, but I'm tempted to give it a go. I imagine stuff like integrating external API's could be really handy, looking through external documentation a…