[flagged]
How many cs are in the word "abacus"?
Write-only code
21–30 of 59 posts
Re: Write-only code
#22He is trying to use a different phrase “write-only code” to define exactly the same thing Karpathy defined last year as “vibe coding”. For what it is worth, in my experience one of the most important skills one should strive to get much better at to be good at using coding agents is reading and understanding code.
I thought "vibe coding" had come to mean "I used an LLM to generate this code", but didn't really imply we'd given up trying to review and read the output. The author is taking it one-step further by suggesting we not bother with the latter.
Re: Write-only code
#23He is trying to use a different phrase “write-only code” to define exactly the same thing Karpathy defined last year as “vibe coding”. For what it is worth, in my experience one of the most important skills one should strive to get much better at to be good at using coding agents is reading and understanding code.
I thought "vibe coding" had come to mean "I used an LLM to generate this code", but didn't really imply we'd given up trying to review and read the output. The author is taking it one-step further by suggesting we not bother with the latter.
A lot of people doing vibe coding can barely (or not at all) understand how to read code.
Re: Write-only code
#24This article assumes that AI bubble will never break, and the prices will never go up. While the major LLM providers are located in USA and China, but mostly USA I can imagine the service becoming a hostage for some political interests, and being blocked for a country or more... This also can become a weapon as creation of invisibly malicious code might be advised by LLMs or even executed by LLMs running loose... So I'd say, copying some other author which I read here, that LLM is an exoskeleton and we're not going anywhere, just being strengthened by it and sped up, and constantly held accountable for the code we together with LLM generate
Re: Write-only code
#25> “AI writes the code” is already true inside many enterprise teams I'm highly doubtful this is true. Adoption isn't even close to the level necessary for this to be the case.
[deleted]
Re: Write-only code
#26Earlier quoted context omitted.
I thought "vibe coding" had come to mean "I used an LLM to generate this code", but didn't really imply we'd given up trying to review and read the output. The author is taking it one-step further by suggesting we not bother with the latter.
A lot of people doing vibe coding can barely (or not at all) understand how to read code.
Sure, but the article is talking about people who can and do read code now but will develop software without reading code in the future. Kind of like you rarely look at the object code that the compiler produces.
Re: Write-only code
#27He is trying to use a different phrase “write-only code” to define exactly the same thing Karpathy defined last year as “vibe coding”. For what it is worth, in my experience one of the most important skills one should strive to get much better at to be good at using coding agents is reading and understanding code.
I thought "vibe coding" had come to mean "I used an LLM to generate this code", but didn't really imply we'd given up trying to review and read the output. The author is taking it one-step further by suggesting we not bother with the latter.
I, too, appreciate the clarification in the term "write-only code".
Re: Write-only code
#28I am old. This immediately triggered "Perl!?" in me... Joke aside: Programming languages and compilers are still being optimized until the assembly and execution match certain expectations. So prompts and whatever inputs to AI also will be optimized until some expectations are met. This includes looking at their output, obviously. So I think this is an overblown extrapolation like many we see these days.
> I am old. This immediately triggered "Perl!?" in me... Same same.
I thought it would be about APL
Re: Write-only code
#29He is trying to use a different phrase “write-only code” to define exactly the same thing Karpathy defined last year as “vibe coding”. For what it is worth, in my experience one of the most important skills one should strive to get much better at to be good at using coding agents is reading and understanding code.
I thought "vibe coding" had come to mean "I used an LLM to generate this code", but didn't really imply we'd given up trying to review and read the output. The author is taking it one-step further by suggesting we not bother with the latter.
It's true that the meaning of "vibe coding" has been somewhat diluted - but the original definition as set forth by Karpathy was to forget that the code even exists (no review, no reading the commits, nothing).
https://xcancel.com/karpathy/status/1886192184808149383?lang...
Re: Write-only code
#30I’ve started doing a quick background check on authors before I dive into their content. This piece starts with the assumption that the writer is closely involved in engineering, but a little research reveals they don't actually work in active software development. I’ll pass on this. p.s. I’m happy to read authors with opposing views. Issue is with people who make claims, without having recent direct experience.
But you can be a software dev even if you do not work in software dev. Plenty of those individuals in open source, for example.