Proposals for extra detail about implementation #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! Here are a few random thoughts on the implementation part. (I read the tutorial part too but have no comments---it looks great!) Let me know if any of this needs more clarification.
The main thing I want to propose is that we build the "core functionality" first---basically the Braid dingus but for Gator---and publish it publicly immediately. No need to wait for the study to be ready. Then we can build the tutorial content and the study instrumentation on top of that.
Also, the next thing to write down about this project IMO is an ordered plan of attack---breaking down the project into tasks and thinking through an initial rough ordering based on their interdependency.