71–80 of 158 posts
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.
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.
You can use AI in different ways, it is extremely good as documentations. Often to understand how a library works you want a specific example, getting that example and having an AI answer questions about particulars has been very valuable to me and often saved me meaningless wandering through other parts of the documentation or the Internet as a whole.
Earlier quoted context omitted.
https://youtu.be/IACHfKmZMr8?si=kiTOU7NpoQEwC6kj&t=45
Can you use text in clear prose, please?
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.
the genz kids are just the first ones who made it broadly acceptable... thank god, because it's a waste of brain cycles without added information - and i'm a native german speaker where it's even more stupid
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.
Every time I've tried to get LLMs to create something they quickly get to the point where they fail miserably. It can do boilerplate, it can do straightforward things which have been done a billion times, it can come up with 50 ideas 10 of which are decent and not obvious... but it can't go beyond a certain complexity, it can't use mildly obscure libraries, it can't get major versions of libraries straight, it invent…
It's not the same human who is doing the same thing over and over though.
I have a toddler. He's learning addition and substraction now. I could had him a calculator or LLM and let him skip the entire learning process and do something productive instead. I don't. Because it'll destroy his critical thinking and ability to do anything productive later in life.
> coding isn’t about the finished product. its a lot like writing This doesn't seem applicable in most contexts. Yes, when I'm coding for fun or purely for learning the finished product is less relevant... but I'd guess the vast majority of code that is written is for a business that _only_ cares about the product. Code is an implementation detail. If (and this is a _big_ if) AI-based coding can increase developer ve…
> even as little as 50% Depending on how you measure that velocity (e.g. including security risks, debugging capabilities, ...) even as little as 5% increase is a no brainer for a business. Whether it's AI, powerful laptops, a fully-fledged IDE, an environment with a good dev experience, anything that gives a few percent increase snowballs into millions over an entire workforce. Whether the current AI capabilities pr…
Those things don't happen because the slowdown required before adoption, and the office politics of convincing everyone to make a change, and then the effort of convincing people that this new thing is what should be changed to.
Earlier quoted context omitted.
OP didn't say money is the only reason things are worth doing, he said that things can be worth doing solely for money. There's a big difference between the two.
To each their own.