If you came in with an architecture/component diagram and a clear set of requirements, you could probably get pretty far from scratch just by prompting. In that case, you've already frontloaded the design and code organization work, and now you're just handing that design to a junior dev (Claude) and saying "go do this."
Discussion
But then you're just doing all of the hard work and the AI gets to do the fun ShadowySupercoding stuff
😭
Yeah pretty much
for me the time savings is if it can boiler plate what ive done, but with small tweaks. generally im using too new of stuff for its training so i have to keep a tight leash but for some things when i know its trained or has enough context i can open up the throttle 😁 anyway, its fun and exciting
Yeah the LLMs don't know a ton about Nostr yet. It's good to be on the bleeding edge.
Can't wait for the #GitRepublic LLM, based upon Aedile. Wish I could use it, today. 😭
Someone who can code and test, who uses this will be a Supercoder. Someone who can't code or test, who uses this will be a Vibecoder.
Dynamic doesn't change, everyone just ups one level.
yes, in my experiences, it has a lot better chance of working when you have a solid, hand-written base that it can infer from.. i like to give it feature work sometimes and see what it can do. its hit or miss, sometimes its really impressive and saves me lots of time, other times it majorly gets in the way and is waste of time.
eventually you get a feel for what it has a chance of doing vs. not. and how to prompt it so it has better chances.