8 ms·

> Vibe coding is opening up a new avenue for custom built functionality that was previously too expensive. I'm not debating that. What I am arguing for is for

by imiric 1y ago

> Vibe coding is opening up a new avenue for custom built functionality that was previously too expensive. I'm not debating that. What I am arguing for is for using these new tools smartly and conservatively, because they have and will continue to produce low quality software in hands of inexperienced developers. It's easy to be misled by their confident tone and the overhyped marketing around them into thinking that they're able to do things they realistically cannot. Those best practices you say that customers don't care about are precisely what help prevent quality issues from impacting them, regardless of the software complexity. Vibe coding throws all of that out the window. It's tempting to cut corners to keep the cost of projects down, but ignoring well established software development practices is not a safe way to do it. > If you really think you can diagnose issues and offer advice based on the quick comment I made, you should reassess your own humility before recommending it to others. I'm not offering advice. I'm going by what you said, and voicing a concern that the apparent utility of LLMs has some important caveats. I don't particularly care about your friend's firm nor their customers. What I do care about is that the widespread adoption of vibe coding is doing more harm than good to the software industry and society at large, which will have destructive consequences in the near future. Instead of engaging with this argument and filling in any details I might be missing, you chose to attack me personally, which says more about you than me.

satyrun 1y ago
How convenient protecting us from the "harm" of LLMs just happens to align with your own self interest. I am sure that isn't causing any bias in your perceptions of reality.
deleted 1y ago
[deleted]
stillpointlab 1y ago
> Instead of engaging with this argument What argument? You are expressing vague feelings of concern and stating incorrect assumptions. I can't change how you feel and those feelings are valid. They are certainly motivating your reasoning and leading you to the incorrect assumptions. You are stating conclusions (e.g. "He will deliver a seemingly working site to his customers with security issues and bugs, and it will only be a matter of time for them to be exploited.") as if you have a crystal ball and then demanding that I defend this figment of your imagination. > What I am arguing for is for using these new tools smartly and conservatively You've moved the goalpost here. You said "These issues could be mitigated or avoided by hiring an experienced developer." Now you are back peddling, suggesting you actually meant to say we should use the tools "smartly and conservatively". So how about you state yourself clearly: Can non-programmers use these tools "smartly and conservatively". And if so, why do you assume the friend I mentioned in question, someone who has been in the business for decades hiring for and delivering software, is incapable of doing so. And if not, provide an actual argument to that effect.

by imiric 1y ago

satyrun 1y ago

How convenient protecting us from the "harm" of LLMs just happens to align with your own self interest. I am sure that isn't causing any bias in your perceptions of reality.

deleted 1y ago

[deleted]

stillpointlab 1y ago

> Instead of engaging with this argument What argument? You are expressing vague feelings of concern and stating incorrect assumptions. I can't change how you feel and those feelings are valid. They are certainly motivating your reasoning and leading you to the incorrect assumptions. You are stating conclusions (e.g. "He will deliver a seemingly working site to his customers with security issues and bugs, and it will only be a matter of time for them to be exploited.") as if you have a crystal ball and then demanding that I defend this figment of your imagination. > What I am arguing for is for using these new tools smartly and conservatively You've moved the goalpost here. You said "These issues could be mitigated or avoided by hiring an experienced developer." Now you are back peddling, suggesting you actually meant to say we should use the tools "smartly and conservatively". So how about you state yourself clearly: Can non-programmers use these tools "smartly and conservatively". And if so, why do you assume the friend I mentioned in question, someone who has been in the business for decades hiring for and delivering software, is incapable of doing so. And if not, provide an actual argument to that effect.