3 ms·

> Being able to code doesn't make you better than the "plebs" who are creating massive value with a vibe coded tool. > [...] I noticed AI could really code be

by vdupras 8mo ago

> Being able to code doesn't make you better than the "plebs" who are creating massive value with a vibe coded tool. > [...] I noticed AI could really code better than me [...] AI code output is generally considered mediocre (in the sense of "on the median"). If it codes better than you, it might be that your code output is generally below average. Might it be the case that you don't grasp how good one can get with computers and thus not realize that one could be much better than you are at programming them? Did you consider for a moment the possibility that you were missing something?

borzi 8mo ago
Notice how I said "coding", not "programming". Coding to me is "should I do an early return or use an if/else? Should I extract that variable into a function to make it cleaner?". It's about focusing on the trivialities that come with insisting on meticulously hand typing and reviewing every line instead of focusing on software quality, design and user needs.
- vdupras 8mo ago
  If we want to make that distinction, then we should also acknowledge that "vibecoding" is a misnomer and should be called "vibeprogramming", because it delegates the whole act of programming to the LLM, leaving you with fleshing out the specs (which is not programming). If that is so, then your whole comment is inconsistent and akin to "I do all my poetry with LLMs now and I don't see what people have against it: it's often better than me at punctuation!"
- philipwhiuk 8mo ago
  > software quality If you think software quality isn't tied to readable (clean) code...
- a_better_world 8mo ago
  Soooo many times in my career I've had to come back and "extract that variable into a function" that I just do it right away by force of habit. Point is, this isn't trivial, it is the kind of thing that ends up saving work over the long haul. Or include this in my agent 'rules' files. GOOD EXAMPLE query=f""" SELECT foo FROM {sometable} WHERE {condition} """ answer=spark.sql(query).toPandas() BAD EXAMPLE answer=spark.sql(f""" SELECT foo FROM {sometable} WHERE {condition} """).toPandas()

by vdupras 8mo ago

borzi 8mo ago

Notice how I said "coding", not "programming". Coding to me is "should I do an early return or use an if/else? Should I extract that variable into a function to make it cleaner?". It's about focusing on the trivialities that come with insisting on meticulously hand typing and reviewing every line instead of focusing on software quality, design and user needs.

vdupras 8mo ago
If we want to make that distinction, then we should also acknowledge that "vibecoding" is a misnomer and should be called "vibeprogramming", because it delegates the whole act of programming to the LLM, leaving you with fleshing out the specs (which is not programming). If that is so, then your whole comment is inconsistent and akin to "I do all my poetry with LLMs now and I don't see what people have against it: it's often better than me at punctuation!"
philipwhiuk 8mo ago
> software quality If you think software quality isn't tied to readable (clean) code...
a_better_world 8mo ago
Soooo many times in my career I've had to come back and "extract that variable into a function" that I just do it right away by force of habit. Point is, this isn't trivial, it is the kind of thing that ends up saving work over the long haul. Or include this in my agent 'rules' files. GOOD EXAMPLE query=f""" SELECT foo FROM {sometable} WHERE {condition} """ answer=spark.sql(query).toPandas() BAD EXAMPLE answer=spark.sql(f""" SELECT foo FROM {sometable} WHERE {condition} """).toPandas()