←back to thread

A Software Development Methodology for Disciplined LLM Collaboration

(github.com)
97 points jay-baleine | 3 comments | 06 Sep 25 10:47 UTC | HN request time: 0.424s | 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 #
1. ianbicking ◴[06 Sep 25 19:06 UTC] No.45152002[source]▶
My experience writing in a professional setting is that people mostly don't read what I write, and the more effort I put into being thorough the less likely that it will be read.
replies(2): >>45152656 #>>45156684 #
2. wheelerwj ◴[06 Sep 25 20:38 UTC] No.45152656[source]▶
That is an interesting observation. You're correct, the LLM inheritly reads and digests ever token you offer it.
3. rapind ◴[07 Sep 25 09:23 UTC] No.45156684[source]▶
Agreed, and I would argue the super quick turnaround time an interactive discussion during a planning phase make this much more enjoyable.

I also enjoy discussing solutions with people in real time too. But writing documentation in a vacuum without any feedback or even knowing if someone will read the spec?? Soul draining stuff.

In fact, the best of both worlds would be having a discussion with someone else (real person) while an AI agent listens, takes notes, and provides feedback / insights using different models. Vetting your ideas etc.