Assignments Due
Week 5 checkpoints should be submitted by Monday, 02/05/2018 at 11:59 PM PST.
Perform
No checkpoint due this week :)
Compose
Individual 1: Big Idea 1 (100%, 10 points)
How should you develop and explain a data science idea? It is as simple, and as difficult, as writing it down. Give your idea a beginning, a middle, and an end. Introduce a problem and whose problem it is. Propose a solution. Describe the difference it makes. A beginning, a middle, and an end. A problem, a solution, and a difference. It’s a structure that is easy to learn but hard to master. So sit down and write, and try to pour your creativity into that simple mold.
Ok, first let’s admit that “finishing touches” has a false air of finality to it. You are still very much at the beginning of documenting your thinking about your data science concept. Don’t worry about feeling unfinished, just try to put a pin in it for now by wrapping up what you have into a respectable–or at least minimally viable–package that you wouldn’t mind showing someone who has an interest in the quality of your work. That’s your instructors and peers for the purposes of W201, but try to imagine writing to a real stakeholder audience who might support (or block!) your idea. After another iteration or two you would be ready to do just that. This week just concentrate on finishing the sprint you’re in with more polish than your first draft.
Your task is to continue writing, and this time to incorporate the issues your peers have left on your repository. Finally, do not lose sight of the original goal of a well-balanced beginning, middle, and end.
How to submit
Make at least one more commit to your 01.Rmd source document, then build your source code into HTML and deploy your portfolio as a website on github.io. Follow the deployment tutorial to learn how.
Review
Participation 1: Peer Review 1 (66%, 3 points)
Workshop in small groups by reading and reviewing the work of a close circle of peers. Using the collaboration functions available through GitHub.com, provide feedback about what they should keep, cut, rearrange, or add to strengthen the composition.
Find the comments left by your peer review circle on the issues page of your portfolio repository. You should curate, rather than automatically implement, the advice of your interlocutors. Only resolve issues that you agree are important, but carefully consider your rationale for rejecting what you feel does not suit your purposes.
How to submit
For each issue left by your peers on your portfolio repository, carefully read and consider their advice. Reply in the issue thread to continue the conversation or to seek clarifications on what they meant. When you close an issue, be sure to make a final comment to document your thinking about how you can usefully incorporate their suggestions, or why you think it is best to take a different (often your original) direction.
Don’t close an issue without a summary comment; your instructors and your future self will thank you. The better your notes are here the easier it will be to incorporate the feedback into your 01.Rmd prose.