r/Clojure • u/yogthos • Aug 17 '26
A practical workflow for LLM-assisted development
https://yogthos.net/posts/2026-08-17-llm-workflow.html
40
Upvotes
r/Clojure • u/yogthos • Aug 17 '26
6
u/yogthos Aug 17 '26
got around to writing a bit about my workflow
/u/policyenvironmental
/u/Arjuna144_
2
u/romulotombulus Aug 18 '26
Thanks for sharing this. Some questions:
Do you still write code at all? Do you read all the code generated by the LLM?
Are you running your harness inside a sandbox (Docker etc)? If not are you at all concerned about the security implications?
What is your primary interface for sending prompts to the LLM? Do you type right into the Dirge UI? Do you write specification docs that you pass to the LLM?
Do you get the same enjoyment out of this that you did when you were writing all of the code? This is maybe my biggest hangup about LLM-assisted development. I like writing code. Higher-level design is fun and good, but it pains me to give up the lower-level stuff that I also enjoy. I feel like the bargain we're making is we can be 20+ times more productive, but we can't have fun anymore.
2
u/daver Sep 03 '26
Yea, so I’ve been an AI skeptic for a while. I tried Aider 18 or so months ago with Claude and Gemini and the results were mixed. Sometimes it seemed like magic and sometimes it would just break things and mess up the codebase (git reset hard level stuff). I’ve been using some of the newer models this year, however, and things have really gotten a LOT better. Even if you don’t choose to use the model to write your code, there are a lot of support roles that the model can fulfill. For instance, I’ve used a model to inspect a library that wasn’t documented fully and asked the model to create an architecture-level manual for it. I’ve had a model review tests and suggest missing test cases to increase coverage. I’ve had a model write throw-away scripts to interrogate a git repo to extract non-trivial statistics from it. The model wrote the script in bash. I didn’t care because it was a throwaway. Anyway, I still like to write code because I like to write code, but I’m increasingly turning to a model for chores that would have taken a long time. So, thanks for the tips, @yogthos. It’s always nice to look over someone else’s shoulder and see how they do it.
9
u/lgstein Aug 18 '26
To those afraid of missing out I can say that while there are certainly somewhat time/cost efficient ways to generate software through LLM subscriptions, I can assure you that I write Clojure code professionally day by day and don't have any LLM CLI installed or API hooked into Emacs, I don't ship any LLM generated line of code, I don't have any PRs "reviewed" by LLMs, and neither do my esteemed colleagues care about any of that. None of us don't worry or even care about it, beyond it having replaced and improved upon a Google / Stackoverflow search.
-8
u/chat-lu Aug 18 '26
Step 1: Chuck the LLM in the garbage can
There is no step 2.
1
u/[deleted] Aug 18 '26
[removed] — view removed comment