25
Thoughts on coding with AI: my experience
(wiki.gardiol.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Nov 2026
25 points (85.7% liked)
LocalLLaMA
5601 readers
152 users here now
Welcome to LocalLLaMA! Here we discuss running and developing machine learning models at home. Lets explore cutting edge open source neural network technology together.
Get support from the community! Ask questions, share prompts, discuss benchmarks, get hyped at the latest and greatest model releases! Enjoy talking about our awesome hobby.
As ambassadors of the self-hosting machine learning community, we strive to support each other and share our enthusiasm in a positive constructive way.
Rules:
Rule 1 - No harassment or personal character attacks of community members. I.E no namecalling, no generalizing entire groups of people that make up our community, no baseless personal insults.
Rule 2 - No comparing artificial intelligence/machine learning models to cryptocurrency. I.E no comparing the usefulness of models to that of NFTs, no comparing the resource usage required to train a model is anything close to maintaining a blockchain/ mining for crypto, no implying its just a fad/bubble that will leave people with nothing of value when it burst.
Rule 3 - No comparing artificial intelligence/machine learning to simple text prediction algorithms. I.E statements such as "llms are basically just simple text predictions like what your phone keyboard autocorrect uses, and they're still using the same algorithms since <over 10 years ago>.
Rule 4 - No implying that models are devoid of purpose or potential for enriching peoples lives.
founded 3 years ago
MODERATORS
Thank you for sharing.
I also tried vibe coding with Qwen3.8 (just give it a few lines of what you want, and step away). and you're right, it does... something, but not at all how you want it. (obvious in hindsight)
Your Step 4 is how I use AI now. I use Deepseek Harness. I don't use a dedicated plan mode, but I do tell it 'let's plan and write a TODO .md for a ', and we discuss ways of implementing something, what libraries we can use, pit-falls, future-proofing etc., and it will write whatever we decide on in a TODO file. Only after each step has been discussed, I tell it to review the TODO and ask me if it has any more questions. Once it's satisfied, I verify what it wrote in the TODO one last time, and when I'm satisfied I tell it to implement the TODO we just planned.
TODOs work quite well if you make and review them with the model before it implements it.
Good idea... Will try that next time