Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for reverse execution #6

Closed
amyjko opened this issue Aug 24, 2017 · 0 comments
Closed

Support for reverse execution #6

amyjko opened this issue Aug 24, 2017 · 0 comments

Comments

@amyjko
Copy link
Collaborator

amyjko commented Aug 24, 2017

We've observed many developers want to "reset" the strategy, starting over from scratch, or winding back to a particular place in the strategy after going down a path that wasn't fruitful, or trying a strategy that isn't encoded in the explicit strategy we provided. Because we don't support this, developers often abandon the systematic strategy altogether, rather than reusing their progress.

I'm torn on whether this is MVP or nice to have. My sense is that if we don't implement this, the tool won't feel complete and developers won't want to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants