Developers question whether proposal addresses the real problem
3 Sep 21 12:10 PM · 4d ago · 1 comment · 1 source · development 3 of 5
Commenters on Lobsters push back on the core premise. cceckman argues the essay frames LLMs as motivation for something that should have been standard practice already (colocating source artifacts with code). bakkot raises practical questions about how to capture the iterative back-and-forth refinement that happens between developer and LLM, which the initial prompts do not capture.
“I don't know how this is actually supposed to work…for anything nontrivial there follows several back and forth rounds where I'm telling it 'actually, rip out the Foo and try just augmenting Bar'…Even if I was capturing these later prompts, they aren't very…”
bakkotBrady Olano Montana State University professor, AI consultant
The whole story postscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 1 voice · verbatim
-
This essay claims: > Markdown is becoming source code, not documentation
All 5 developments of Montana State prof proposes /src/md directory for… →
Hacker NewsLobstersMastodon