Stat 370 2017S Post Mortem
From Sean_Carver
As STAT 370 draws to a close, it is time for analysis of what went well, and what could be done better.
What went well
- Flexible projects: I believe that the only reasonable way to learn to code is with projects you are passionate about. I encouraged students to find such a project and some, if not many did. I gave them about as much flexibility as possible to pursue their dreams. If students found a topic interesting, I wanted them to pursue it and I did not want to stand in their way. I did however steer students toward original projects, not just repeating analyses done by others. I believe that students who felt the passion certainly benefited from it. And the ones that did not fall in love with their topic were probably not hurt by the flexibility I gave them.
- Reproducible Research and dynamic documents: I experimented with these course objectives and I would definitely make this a part of the course if I teach it again.
- Course work posted on a web server: I feel very certain that this was the right way to go. I had the idea for a web server in the middle of the semester, when students told me they wanted to
- Github:
What could done better =
- Instructor learning topics on the fly:
- Too much instructor troubleshooting and debugging:
- Not enough graded homework assignments:
The jury is still out =
Data visualization, Shiny, Plotly:
