I started with a new workflow where before I start coding I would do Discovery session where I say discovery explicitly and try to give it most of the context I know, chats task items, things and edge cases I am thinking of in my head. The results were wonderful. Tasks started getting done faster and cleaner.
Does the plan step take your own edge cases and context in first, or does it plan straight from the goal?
Pretty much the same instinct, yeah. There's a "Discuss first" box when you start a task. If you tick it, it reads around the repo first and tells you what it thinks you mean, what it's unsure about and what it's assuming. Then you just talk it through and dump your edge cases in before it plans anything. I use it on anything that isn't trivial; the plans come out a lot better.
And if you realise halfway that the plan's wrong, you can say so and it re-plans from where you are.
I think the scar tissue built from getting things wrong and figuring it out from scratch is just as important if not more than actually getting something done. When I first implemented AI into my workflow, I tried something similar but it just didn't stick. Now I use it to work out the less important boilerplate that I just can't be bothered with and do everything else manually.
I started with a new workflow where before I start coding I would do Discovery session where I say discovery explicitly and try to give it most of the context I know, chats task items, things and edge cases I am thinking of in my head. The results were wonderful. Tasks started getting done faster and cleaner. Does the plan step take your own edge cases and context in first, or does it plan straight from the goal?
Pretty much the same instinct, yeah. There's a "Discuss first" box when you start a task. If you tick it, it reads around the repo first and tells you what it thinks you mean, what it's unsure about and what it's assuming. Then you just talk it through and dump your edge cases in before it plans anything. I use it on anything that isn't trivial; the plans come out a lot better.
And if you realise halfway that the plan's wrong, you can say so and it re-plans from where you are.
I think the scar tissue built from getting things wrong and figuring it out from scratch is just as important if not more than actually getting something done. When I first implemented AI into my workflow, I tried something similar but it just didn't stick. Now I use it to work out the less important boilerplate that I just can't be bothered with and do everything else manually.
[dead]
[flagged]