2019 Course Material - sketch about syllabus HOT 5 CLOSED

Looks good. What I recognized on a first look:

General Schedule on allocation between us

Week 1:

• I'm under the first Python session on Wednesday afternoon - copy paste or intention?

Week 3:

• You do R: Econometrics. That's coding your own function for applications?
• I do advanced R: That's cleaning up code? Functions would probably already be covered in the Econometrics sections - correct?
• Automation 50/50: I guess that's intention?

Move Git

Good idea. Might be more attractive to the students. The only possible negative consequence I see is that they might have forgotten much bash by then and could experience some frustration. However they only need to move around, visualize folder content and copy / move files. In general this should be a minor problem and a chance to refresh bash basics again.

3rd person

• Starting with an advanced session could be complicated as a start.
• Maybe rather a basic session?

from syllabus.

In response:

Week 1

• typo - updated in an edit

Week 3

• R metrics is a lfe and other stuff related to estimating models... if youre comfortable happy for you to do it rather than I
• Advanced R - not totally sure hence the ambiuous name... definitely command line parsing thou
  • could also think about writing own function libraries etc, or some serious attempt at functional programming with purrr
• Automation - 50/50 is purposeful for now ... might be updated once we figure out what the third person is comfortable with
  • for syllabus to distribute we don't need to add names for now

3rd person

• Potentially a good idea to have them to the basic stuf... really depends on what they know

moving git

• See below for an iteration

PS. don't tag a number with a # -- it links to an issue with that number ;)

from syllabus.

Version with Git coming later .... put it before the python project so that they can use the project to also play with git for the first time

from syllabus.

Week 2

• you have version control 3 - prolly a typo again
• Having version control between python and the project looks odd. I understand that version control should be part of the project. Could the rapid change back and forth be problematic?
• should the python project be on a single day or is a half day half day split better?

Week 3

• I'm OK with LFE (and Stargazer). Prolly depends on the other tools to be shown / used
• Parsing stuff with R and cleaning up previous scripts would probably fill a whole session for "Advanced R". It also is a good preparation for the following R project and build tools. Do we have an equivalent for Python?

from syllabus.

Week 2

• version control 3 - yep typo - edited
• not sure about if we want version control there or after python project ... not a huge deal for now
• not sure split over two half days really matters either ... but if shift version control afterwards then i guess this goes away

Week 3

• Metrics - we can split it based on relative comfort
• Advanced Python will be the equivalent session

from syllabus.