Why I don’t vibe code
111–119 of 119 posts
Re: Why I don’t vibe code
#112Earlier quoted context omitted.
People have a very strong tendency to go "current gen technology cant achieve x, therefore its impossible for this class of technology to ever achieve x" Many many many of the problems with current gen ai will go away.
Ah, the classic "But just you wait, the next version will be better!" fallacy. It's a fallacy because the reality is often not that…in fact sometimes the reality ends up worse. (See "enshittification", a process whereby technology gets worse over time, not better.)
You’re again conflating the product offerings from the capacity of the technology. It’s like kinetic energy vs potential energy.
The real wait is for the cost in disk space, memory and electricity of pretraining a transformer to be something the equivalent of a raspberry pi can accomplish. Then all the style and design choices of the few current vendors goes away.
Re: Why I don’t vibe code
#113Earlier quoted context omitted.
> virtually everyone building a startup uses these tools to automate a huge chunk of the work. you have no real chance otherwise. Huh? Do you mean people "building a startup" without any experience at all ? The list of tasks in the comment you're replying to are well within the skillset of any software engineer that has that old job description classic "3 to 5 years experience". Not to be rude, but if the code is the…
Where did I say that you didn't need to already have the skillset in order to build something with it? It's just a force multiplier. And learning to use these tools effectively is a skill of it's own. I'll never understand why folks on here look at this tech in such black and white. Of course it has no concept of logic or understanding. But if you do, you can bring out whatever is in your head out into code at 10x th…
> ... slow and thorough
Yes, we all know LLMs can't write code worth a shit unless the dev guiding it knows exactly what they need.
You're the one insisting we don't type fast enough to keep up with competition. I am saying coding is not typing and problem solving is trivially easy if you already have experience solving those problems. Hence my original question.
There's never been anything slow about writing code even long before LLMs. The slow part is figuring out what you need to do. LLMs don't help you there.
Re: Why I don’t vibe code
#114I thought this was going to be an article about intelligent use of LLM tools without vibecoding, but it's actually entirely against LLMs altogether. The person who wrote it used a free trial of some tool (most likely not a frontier model) and then gave up forever when the trial ran out. > I then tried using one of the AI tools to analyze my code in a project and a few other small tasks before it all came to an awkwar…
Re: Why I don’t vibe code
#115Earlier quoted context omitted.
If they want to continue that practice that's fine but they will quickly find that it severely limits their options for participating in the software industry.
If you've all been reduced to vibe coding and hoping for the best I'd suggest that you aren't really participating in the software industry either mate.
Making code is not synonymous with making software.
Re: Why I don’t vibe code
#116Re: Why I don’t vibe code
#117I'm vegan. I only watch PBS and the Criterion Channel. I'm atheist. Now it's "I don't vibe code."
It does seem like a sort of virtue signaling these days right?
Re: Why I don’t vibe code
#118Re: Why I don’t vibe code
#119Earlier quoted context omitted.
It does seem like a sort of virtue signaling these days right?
Do you think people can't care about things or have ethical standards without "virtue signaling"? It seems like a lot of people do think so. Or maybe this is a form of "vice signaling"