zlacker

>>gmays+(OP)
So, can anyone point me to a video where someone is doing this to produce something meaningful, real world stuff? I want to see the requirements being decided upfront, followed by the prompting and then "coding" by the agents. Not some, fly by the seat of my pants and we stop when "it kinda looks okay" thing. E.g. an end-to-end SaaS or whatever non-trivial.

>>pan69+Whd
I use AI every day to write stuff.

Last night I needed a C# console app to convert PDFs to a sprite sheet. I spent 30 seconds writing the prompt and another 30 seconds later the app was running and successfully converting PDFs on the first try. I then spent about another 2 mins adding a progress bar, tweaking the output format and moving the main logic into a new library.

>>qingch+NNe
Sure. I do that too. However, the article talks about something very different. What you describe is Stage 2 or 3 as listed in the article. I want to see a demonstration of Stage 8 in action.

> First, you should locate yourself on the chart. What stage are you in your AI-assisted coding journey? > Stage 1: Zero or Near-Zero AI: maybe code completions, sometimes ask Chat questions > Stage 2: Coding agent in IDE, permissions turned on. A narrow coding agent in a sidebar asks your permission to run tools. > Stage 3: Agent in IDE, YOLO mode: Trust goes up. You turn off permissions, agent gets wider. > Stage 4: In IDE, wide agent: Your agent gradually grows to fill the screen. Code is just for diffs. > Stage 5: CLI, single agent. YOLO. Diffs scroll by. You may or may not look at them. > Stage 6: CLI, multi-agent, YOLO. You regularly use 3 to 5 parallel instances. You are very fast. > Stage 7: 10+ agents, hand-managed. You are starting to push the limits of hand-management. > Stage 8: Building your own orchestrator. You are on the frontier, automating your workflow. > *If you’re not at least Stage 7, or maybe Stage 6 and very brave, then you will not be able to use Gas Town. You aren’t ready yet.*