pull down to refresh
0 sats \ 0 replies \ @rizzling 21 May \ parent \ on: Devs: LLMs are not about to take your jobs devs
its iterative. and it defenitly needs a bunch of scripts to handle the communication with the API and the command execution. there are some tools like gpt-engineer or gpt-pilot, which - unfortunately - dont work very well. the approach is not low enough imo.
definetly use a vm, some good bash scripts for the api requests with the right parameters to get a response which has some specific synthax so that it can be parsed effictively. use the response to either execute commands (downloads, file creation etc) or request more client input (since 4o this can be even the client infront of a camera ;)). than use the console logs and other relevant log data for the next iteration. sorry for the very rough explanation, but I think it's enough to understand why the process can potentially produce not just couple of mils, no I mean mire like 100mil+.
oh and possible but NOT recommended for obvious reasons: its no problem to even involve a wallet/payment data and give gpt the ability to create other vms in the google cloud and deploy and get a domain etc.