←back to thread

A Software Development Methodology for Disciplined LLM Collaboration

(github.com)
97 points jay-baleine | 2 comments | 06 Sep 25 10:47 UTC | HN request time: 0.402s | source
Show context
perrygeo ◴[06 Sep 25 14:54 UTC] No.45149798[source]▶
There's some irony; far from handling the details, LLMs are forcing programmers to adopt hyper-detailed, disciplined practices. They've finally cajoled software developers into writing documentation! Worth noting we've always had the capacity to implement these practices to improve HUMAN collaboration, but rarely bothered.
replies(5): >>45150398 #>>45150447 #>>45151153 #>>45151726 #>>45152002 #
grork ◴[06 Sep 25 15:57 UTC] No.45150398[source]▶
We’ve ultimately decided to treat the models with more respect, nurturing, and collaborative support than we ever did our follow human keyboard smashers. Writing all the documentation, detailed guidance, allowing them multiple attempts, to help the LLMs be successful. But Brenda, the early in career new grad? “please read this poorly written, 5 year-old, incomplete wiki, and don’t ask me questions”

I’ve been thinking about this for months, and still don’t know what to make of it.

replies(3): >>45150627 #>>45151425 #>>45152046 #
1. ianbicking ◴[06 Sep 25 19:11 UTC] No.45152046[source]▶
Respect (or lack thereof) goes both ways: both the writer and reader. I have frequently felt disrespected by producing documentation, planning/etc that isn't read. In the end I mostly rely on oral transmission of knowledge because then at least I can read the room and know if I'm providing some value to people, and ultimately we're both trapped in the room together and have to invest the same amount of time.

The LLM isn't always smart, but it's always attentive. It rewards that effort in a way that people frequently don't. (Arguably this is a company culture issue, but it's also a widespread issue.)

replies(1): >>45153634 #
2. perrygeo ◴[06 Sep 25 22:51 UTC] No.45153634[source]▶
Great framing of the problem. I do think it's a culture issue with "Agile" practices in particular - By design, there is no time budgeted for reading, writing, reflection, or discussion. Sprint, sprint, sprint.

In organizations that value innovation, people will spend time reading and writing. It's a positive feedback loop, almost a litmus test of quality of the work culture.