Developer argues colocated artifacts should precede LLM era
4 Sep 21 12:13 PM · 4d ago · 1 comment · 1 source · development 4 of 5
cceckman notes that the practice of keeping source artifacts (decision records, lab notebooks, experiment logs) alongside code is not new and should not require LLMs as justification to implement it.
“It's strange to me that LLMs seem to motivate this, instead of 'your source artifacts should live with your code...' Yeah, someone trying to understand the code needs access to all those; make it accessible to them.”
cceckmanBrady 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
-
It's strange to me that LLMs seem to motivate this, instead of "your source artifacts should live with your code..." ...and source artifacts include [decision records](https://adr.github.io/) of [various sorts](https://rfd.shared.oxide.computer/), lab notebooks used to run experiments, etc. Yeah, someone trying to understand the code needs access…
All 5 developments of Montana State prof proposes /src/md directory for… →
Hacker NewsLobstersMastodon