MikeSharp01 Posted Monday at 12:46 Posted Monday at 12:46 12 minutes ago, Pocster said: Bit like giving an 8 yr old a chainsaw and then telling them to chop trees…. You might see it that way BUT there is very little research I have seen that shows that people without any coding skills can drive LLM code developers successfully - ie taking the basic output of requirements engineering, in English if you like, and just expecting a fully worked solution. So I speculate that what we have is apparent, stress apparent, productivity improvements for the coders that are left but where that productivity as measured by the normal metrics is coming out much less than expectations and that may in the medium term, because of maintainability, be even less. This is not to say I would advise cutting back on LLM coding but rather seeing it for what it is - more of a challenge than expected as it is now. The advent of more " agentic" LLM coding along the road Codex seems to be heading will change the perspective again. Anyways it's all good clean fun and I am off for cream cakes and lashings of ginger beer - tallyho. 1
Pocster Posted Monday at 14:20 Author Posted Monday at 14:20 1 hour ago, MikeSharp01 said: Anyways it's all good clean fun and I am off for cream cakes and lashings of ginger beer - tallyho. Why not! Its hot! I'm in the garden fighting chat. I actually got it to say "I cant do it we need a coder with repo access". I beat the bitch into submission. We'd been trying and failing for 15 minutes. I asked it what it needed. Gave me a 'sed','tail','cat' answer. I did it manually in terminal uploaded it. 60 seconds later fixed. But yes "no coding skills" with an LLM is only going to get you toy stuff. Remember OpenAi said 70% of chat is written by chat and they expect that to be 100% soon. So the SE/coder role now changes to LLM manager/architect/controller. But yes ; I assume even Claude can get it's knickers in a twist! But from how I was using chat just 12 months ago (and its capability then ) to today is phenomenal ! We go do rabbit holes and poor design decisions. Sometimes it does things I didn't ask and when I find out later I tell it where to go! But! - what I am achieving in terms of work flow with zero human coding is pretty magical even if not completely local yet. Imagine where it will all be just 12 months from now! Oh! , I can hear the clink of ice in a G n T .......
Pocster Posted Monday at 15:50 Author Posted Monday at 15:50 Then you get sweet moments where 15 patches all go straight through 😎
Pocster Posted 19 hours ago Author Posted 19 hours ago (edited) Awesomeness! Refined the harness code ( I.e told chat it was shit ) - patches approval really high now . Implemented but not ‘ voice ‘ tested … ” play Coldplay “ ” play head full of dreams “ ” play that Coldplay album I played last Tuesday “ ” what Coldplay albums do I have? “ ” play something by Coldplay “ etc etc nice and broad . Also if you mis say or more likely it mis heard “ foldplay” will ask if you meant “ Coldplay “ Again not linked into the whisper transcript yet - just fuzzy qwen:3b ‘guessing’ based on intent and what’s in my LMS database . Currently adding Postgres database functionality Edited 18 hours ago by Pocster
SimonD Posted 5 hours ago Posted 5 hours ago On 25/05/2026 at 16:50, Pocster said: Then you get sweet moments where 15 patches all go straight through 😎 It's nice when that happens. And then it all goes wrong with a single update - I just had an entire afternoon and evening trying to resolve a bug, eventually it was a single line of code causing double parsing of the string from the DB. Essentially the code was parsing something already parsed automatically by Postgres and it was looking in the wrong files to fix the bug. It's these days that drive you potty. 1
Pocster Posted 3 hours ago Author Posted 3 hours ago (edited) 1 hour ago, SimonD said: It's nice when that happens. And then it all goes wrong with a single update - I just had an entire afternoon and evening trying to resolve a bug, eventually it was a single line of code causing double parsing of the string from the DB. Essentially the code was parsing something already parsed automatically by Postgres and it was looking in the wrong files to fix the bug. It's these days that drive you potty. LOL! I understand exactly what you mean and exactly that bug. But as I've said to date not had to look at 1 line of code. Chat provides the patch but we have a array of multiple tests it has to pass. If it fails the tests etc I get an output file of why. This is then chucked back at chat where it either does another patch or a better scout. I've added stuff to the pi harness to reduce failing patches quite substantially e.g. pi can now grep/sed/tail files into its prompt for local 120b scout. Commits only happen when I say so. Ledger updates must match i.e. what we did, what was tested, what was commited. Basically so many guardrails that any patching applied has to be rock solid. I spend 90% of my time after supplying the spec/task pressing '7' to scout or '2' to apply patch. A few copy n pastes when chat gets pissy and stuck i.e. it tells me what it needs and I do it manually. TBH it's working really well. Soon I'll tie this into the 1st version of voice transcript and upload a demo. Here's where I spend most my time! Edited 3 hours ago by Pocster 1
SimonD Posted 2 hours ago Posted 2 hours ago (edited) 28 minutes ago, Pocster said: LOL! I understand exactly what you mean and exactly that bug. But as I've said to date not had to look at 1 line of code. Chat provides the patch but we have a array of multiple tests it has to pass. If it fails the tests etc I get an output file of why. This is then chucked back at chat where it either does another patch or a better scout. I've added stuff to the pi harness to reduce failing patches quite substantially e.g. pi can now grep/sed/tail files into its prompt for local 120b scout. Commits only happen when I say so. Ledger updates must match i.e. what we did, what was tested, what was commited. Basically so many guardrails that any patching applied has to be rock solid. I spend 90% of my time after supplying the spec/task pressing '7' to scout or '2' to apply patch. A few copy n pastes when chat gets pissy and stuck i.e. it tells me what it needs and I do it manually. TBH it's working really well. Soon I'll tie this into the 1st version of voice transcript and upload a demo. Here's where I spend most my time! I clearly need to be a bit more disciplined and sort this side out. I've been finding some real limitations with not working locally and version management. I haven't given it access to my local machine so this is definitely causing some friction and the Claude project area has some serious limitations. As I found out, I uploaded all my project files into the depository, but then found out that as soon as Claude does a re-write/patch or whatever edit of the file, it provides an output for download but doesn't update the project file. Then it goes back to use the project file without telling you, ignoring the new output. Even with clear instructions to check with me the latest deployed files, it sometimes completely forgets, completes a new write and output and some of the earlier code is then missing - VS Code deploy version comparison has been a bit of a godsend). I'm currently on very clear instructions and when it creates a new output, I still upload the deployed file to ask it to check the versions are consistent. Now, this is okay for small stuff, but it becomes a right PIA on anything larger (although it still saves hours, weeks and months of human time in what it's able to output - I'm just getting spoiled nowadays). And another little bug I found is that sometimes, if I select download all for the new artifacts, some of the contents are actually previous versions, not what has just been produced! So, having learnt what it takes to prompt, I'm now working out the next step which you've clearly nailed. Edited 2 hours ago by SimonD 1
SteamyTea Posted 2 hours ago Posted 2 hours ago The thought of being trapped in @Pocster's basement with no stimulus, apart from Coldplay, makes me want to walk out to sea and not return. 1
Pocster Posted 2 hours ago Author Posted 2 hours ago (edited) 56 minutes ago, SimonD said: I clearly need to be a bit more disciplined and sort this side out. I've been finding some real limitations with not working locally and version management. I haven't given it access to my local machine so this is definitely causing some friction and the Claude project area has some serious limitations. As I found out, I uploaded all my project files into the depository, but then found out that as soon as Claude does a re-write/patch or whatever edit of the file, it provides an output for download but doesn't update the project file. Then it goes back to use the project file without telling you, ignoring the new output. Even with clear instructions to check with me the latest deployed files, it sometimes completely forgets, completes a new write and output and some of the earlier code is then missing - VS Code deploy version comparison has been a bit of a godsend). I'm currently on very clear instructions and when it creates a new output, I still upload the deployed file to ask it to check the versions are consistent. Now, this is okay for small stuff, but it becomes a right PIA on anything larger (although it still saves hours, weeks and months of human time in what it's able to output - I'm just getting spoiled nowadays). And another little bug I found is that sometimes, if I select download all for the new artifacts, some of the contents are actually previous versions, not what has just been produced! So, having learnt what it takes to prompt, I'm now working out the next step which you've clearly nailed. Chat still ignores things which it gets in it's prompt still! The 'loop' is everything goes back to chat. Ledger, patch outcome, scout etc etc etc. I'm just human doing boring stuff in the middle that creates project but writes zero code. Because my ambition was i do ZERO code we need a tight and rather repetitive loop. My assumption is that Claude nails this in a far better way. But chat with pi as repo scout just requires drag n drop of output files into chatgpt window. I was thrown by codex thinking it was chat but with repo access. But it isn't. It can patch etc but it doesnt understand the project and its structure. ChatGPT does - proves it constantly even if it has the odd wobble now and again. @SimonD I'm confused what the issue is TBH. Claude see's the repo thats the best bit. I have to use local llm to scout repo to uload to chat. Also I naturally assume Claude better reasoner and coder than chat. So I'd assume this arrangement would work better tbh. After all I'm doing a 'poor mans' claude code Edited 1 hour ago by Pocster
SimonD Posted 1 hour ago Posted 1 hour ago 8 minutes ago, Pocster said: @SimonD I'm confused what the issue is TBH. Claude see's the repo thats the best bit. I have to use local llm to scout repo to uload to chat. Also I naturally assume Claude better reasoner and coder than chat. So I'd assume this arrangement would work better tbh. I haven't given Claude access to the repo, so there's quite a bit of manual stuff - but the issues are bugs that require a lot of oversight - e.g. not updating the project files after an update, and referring back to superceded files in memory. Yes, the coding is amazing, and the commenting is on another level so very easy to navigate the code where necessary. It's just these bugs that create workflow friction. Now, if I was brave enough to provide access to the repo, we'd probably be in a different place. 1
Pocster Posted 1 hour ago Author Posted 1 hour ago Just now, SimonD said: I haven't given Claude access to the repo, so there's quite a bit of manual stuff - but the issues are bugs that require a lot of oversight - e.g. not updating the project files after an update, and referring back to superceded files in memory. Yes, the coding is amazing, and the commenting is on another level so very easy to navigate the code where necessary. It's just these bugs that create workflow friction. Now, if I was brave enough to provide access to the repo, we'd probably be in a different place. Lol. Mines a hobby not "real" like yours. But my issue even with previous projects and chat was lack of repo access. Go on give claude repo access just to look/report. BE BRAVE!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now