The lack of respect software developers have for their craft confounds me every day, to the point that I wonder if anyone in software actually writes code because they enjoy it, instead of making money.
>In that future world (which for some of us is already here), what meaning does the term “vibecoding” have anymore? If all coding is AI-assisted won’t it just be referred to as… “coding”?
Apply the same question to music, or drawing, and perhaps the answer to this will be easier to see. If AI continues to improve I think it's much more likely that all human-written code in the future will be 100% human written. Vibecoding or any human-in-the-loop approach seems like a very intermediate paradigm.
Then again this post seems to be a few months old, so perhaps it's understandable that they weren't "feeling the AGI" as severely as we have been the past few weeks.
Why asking outside the technical domain? Code is instructions for a machine for it to do a task. All this philosophy around code as art or whatever it's in my opinion just intellectual onanism, looking at the screen and thinking "damn I'm the shit just look at that oneliner oh my gawd, look at those perfectly applied GoF patterns. Pure engineering. Poetry is code".
The craft you say. What's the intent of it? Having code that's nice to look at and/or understand or the product of such code execution? For the later coding "as craft" is irrelevant. I've seen beautiful and mind blowing software with horrendous code, an entire company working as a clock with a 4 millions LOC single php file, the most cringe inducing spaghetti code I've ever seen. Users don't care. The software works as expected, fast, almost no bugs after >10 years of development. It's purpose fulfilled. And I've seen perfect code running slow as fuck.
I've done manual and CNC machining. I forgot the last time I wrote G codes in the thousands LOC. Everything now is CAD CAM. A software wrote the code for me, I just designed the thing. Same with 3D printing. Should I write the code myself to respect the craft? Of course not, that would an incredible waste of time. I want the physical piece in my hand or an application running fast and without crashing. Why would I care for HOW the code is written?
monospacegames · · focus · HN ↗
>In that future world (which for some of us is already here), what meaning does the term “vibecoding” have anymore? If all coding is AI-assisted won’t it just be referred to as… “coding”?
Apply the same question to music, or drawing, and perhaps the answer to this will be easier to see. If AI continues to improve I think it's much more likely that all human-written code in the future will be 100% human written. Vibecoding or any human-in-the-loop approach seems like a very intermediate paradigm.
Then again this post seems to be a few months old, so perhaps it's understandable that they weren't "feeling the AGI" as severely as we have been the past few weeks.
aeve890 · · focus · HN ↗
Why asking outside the technical domain? Code is instructions for a machine for it to do a task. All this philosophy around code as art or whatever it's in my opinion just intellectual onanism, looking at the screen and thinking "damn I'm the shit just look at that oneliner oh my gawd, look at those perfectly applied GoF patterns. Pure engineering. Poetry is code".
The craft you say. What's the intent of it? Having code that's nice to look at and/or understand or the product of such code execution? For the later coding "as craft" is irrelevant. I've seen beautiful and mind blowing software with horrendous code, an entire company working as a clock with a 4 millions LOC single php file, the most cringe inducing spaghetti code I've ever seen. Users don't care. The software works as expected, fast, almost no bugs after >10 years of development. It's purpose fulfilled. And I've seen perfect code running slow as fuck.
I've done manual and CNC machining. I forgot the last time I wrote G codes in the thousands LOC. Everything now is CAD CAM. A software wrote the code for me, I just designed the thing. Same with 3D printing. Should I write the code myself to respect the craft? Of course not, that would an incredible waste of time. I want the physical piece in my hand or an application running fast and without crashing. Why would I care for HOW the code is written?
aogaili · · focus · HN ↗
I think folks in the craft need to mature a bit and understand this very well.