Vibe Coders might be serious, but I cannot take them seriously, especially when they say "It is a must-have skill".
-
Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no 'best' solution.
wrote last edited by [email protected]Would you visit a house built by vibe architecting? Me neither.
And as soon as the vibe software goes online, your users will not be the only victims anymore.
-
Has anyone else noticed a sudden surge of ads for AI-powered website building tools?
No. Adblocking helps tremendously with that.
-
Of course there's a best solution.. it's whatever you end up with
Not for the users. Do your software right or don't do software, please.
-
"Coding" vs "programming" is such a great litmus test for whether someone actually knows what they're doing
I usually use the term coding to avoid the whole "html isn't a programming langauge" stuff.
-
different strokes for different folks. I enjoy a fresh clean project that I can start with. I hate picking up someone else's mess so using AI in that manner completely goes against what I enjoy as a dev.
it originally sounded to me like you were having AI generate the hierarchy and project structure, but it sounds like you're just using it to generate file templates.
Thanks for the insight.
Same, writing from scratch is so much easier than trying to parse soup code that I or someone else made a while ago.
-
And a glorified auto-complete might be part of a solution, but it isn't the solution itself. And definitely not the best one.
Exactly! auto complete is helpful, but it can cause problems and can't be relied on.
-
I'd guess most of them aren't even capable of actually writing functional and good code themselves. And never will be.
I can write bad and unfunctional code all by myself thank you very much.
-
Vibe coders wishfully think AI could be the end product. AI is a tool, it should never be the final product nor exposed to the user.
It's a fancy autocomplete to throw ideas against, you still need to know what the fuck you're doing, and vibe coders have no clue. This means we're now concerned about a rise in vulnerable code.
As well as unmaintainable code, and in countries with good employment laws and/or employers, extremely unproductive employees. And a whole new generation split between skillful and LLM users.
-
I usually use the term coding to avoid the whole "html isn't a programming langauge" stuff.
The only people saying that are pedants who maybe passed a python crash course. In industry no one gives a shit.
Edit: except that engineer is a protected term in some countries
-
As well as unmaintainable code, and in countries with good employment laws and/or employers, extremely unproductive employees. And a whole new generation split between skillful and LLM users.
That's right. My concern is also that LLM users may shadow skilled programmers in the short term, potentially devaluing their skills or putting some of them out of a job, at least until the LLM-built code starts shitting itself and they crawl back to actual programmers for help.
-
Would you visit a house built by vibe architecting? Me neither.
And as soon as the vibe software goes online, your users will not be the only victims anymore.
And who will? You are crediting too much on the idiotic trend. Nobody has successfully used it
-
That's right. My concern is also that LLM users may shadow skilled programmers in the short term, potentially devaluing their skills or putting some of them out of a job, at least until the LLM-built code starts shitting itself and they crawl back to actual programmers for help.
Look at it positively: Even if many skilled programmers get fired, it's not like most of us won't survive. And once the bubble pops, we're the ones needed the most. Including getting headhunted and good salaries.
-
Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no 'best' solution.
Bro is so committed to the
repobit that he made me cry -
Yes.
I “vibe code” anything that is throwaway. If it’s throwaway code I don’t care about the quality, I just want the end result.
For everything else, I don’t vibe code.
There are definitely people who use AI as a crutch for their lack of technical skills. It’s the same folks who used to try to get coworkers to “help” and slowly built their tickets by cycling through teammates.
I “vibe code” anything that is throwaway.
Same here. It's surprisingly easy to get quick results with a few prompts for one-time scripts without putting any effort in.
-
Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no 'best' solution.
"Googling a lot while coding" is not even remotely close to vibe coding, please don't gaslight yourself into that.
When you read up on things, you know what you're looking for. You read a potential solution (e.g. part of a documentation, an example, someone else's solution, a solution to a similar problem), you think about it and transfer that to your own problem, with your own code, with your own thoughts.
Using AI support is totally fine too - it's a smarter code completion, nothing more. It might spit out something wrong, something partial, something good. You might ignore it as with the regular completion. In the end, it's still you thinking about it, modifying it until it works, and doing your thing.
"Vibe coding" is basically saying tech jesus take the wheel. And it might go well for someone who cannot code, who managed to create their small game or some website. It will go horribly wrong for any project handling user data, sensitive data, or something that needs to be maintained after. We've had more than enough examples of that.
