10 ms·
one wrote code while the other is used by meatbags to write code. why is this example always marched out like it means something?
by dylan604 4mo ago
one wrote code while the other is used by meatbags to write code. why is this example always marched out like it means something?
- LPisGood 4mo agoAlmost all ways of creating programs are effectively just using tools to produce code. Compiling, transpiling, interpreting byte code, etc.
- dylan604 4mo agoagain, that's not what we are talking about here. we have humans writing code using an IDE. we have LLMs generating code that is placed in the IDE. why are people obtuse to this? why are bots obtuse to this?
- LPisGood 4mo agoWe have humans writing code using prompts. We have interpreters generating byte code that is placed in the JVM. I don’t think it’s obtuse to look at it this way.
- khuey 4mo agoClaude didn't "write" anything until a meatbag told it to.
- dylan604 4mo agoMy employer didn't write anything until they told me to.
- zahlman 4mo ago> one wrote code while the other is used by meatbags to write code. One is not a "meatbag" while the other is not a "meatbag". And no, outputting something on stdout that happens to function as code is not "writing" it in the sense that we actually care about here. That's conflating the metaphor we use in describing program behaviour with the actual "meatbag" activity. > why is this example always marched out like it means something? Because it obviously does.