#literatedevelopment — Public Fediverse posts

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

#AMLD Agent-Mediated #LiterateDevelopment methodology first draft, ready to be tested.
I would love some feedback.
https://hg.sr.ht/~travisfw/amld-method
#agenticCoding

I just began an #AMLD repository.
It is a template for Agent-Mediated #LiterateDevelopment methodology.

In a nutshell:
Design documentation and project management should be *on trunk* (or main branch) and must be enough to regenerate everything that has been previously generated with an #AI coding agent. It should be written for humans, except for a log of previously followed plans referenced by closed tickets.

IE the docs are code.

This is not #VibeCoding; this is literate.

Whether you agree with, hate, or are turbulently navigating the transition of many teams to agent-mediated coding (I am considering the post from @anildash where he talks about #codeless, IE #LiterateProgramming or #LiterateDevelopment), Robert C Martin's book, Clean Code should be the bible in these times.

https://sfba.club/user/travisfw/comment/41400

https://www.goodreads.com/work/quotes/3779106-clean-code-a-handbook-of-agile-software-craftsmanship-robert-c-martin

#AIDev

@anildash I do have a better term than #codeless!
I mean Donald Knuth does: #LiterateProgramming.
AI is new, but everything about what the developer does is, well, let's call it #LiterateDevelopment, just a slight shift into this millennium, reflecting that it really becomes enough to develop a system, still obviously referencing Knuth.
I think the word "literate" emphasizes the care and responsibility a dev should take not to produce slop.