tayaadmin.blogg.se

Cogs 18 ucsd
Cogs 18 ucsd







cogs 18 ucsd

My goal will be to get closer to 100% of the class self-reporting a 3.Ĭheck all that apply: After COGS 18, which of the following skills do you feel you possess?īeyond general student comfort level, I’m always curious about how well I’ve accomplished my course objectives.ĭuring the quarter, I sensed that students struggled in the last few weeks of the course when we focused on best practices in Python and using the command line (rather than Jupyter notebooks). It is my expectation that students leave this course rating themselves a 3 out of 5 Anything higher is great, but not my expectation. It’s my goal that students move away from novice in the direction of expert.

cogs 18 ucsd

I am very clear with students on the first day of class that I do not expect them to become a programming expert in 10 weeks. In the beginning of the quarter in this class, 60% of students typically have no programming experience. This past Spring (Spring 2020), >90% of the class responded that they are at least a 3. With this, we see a slight shift in students’ comfort, with more students reporting that they are a 4 out of 5 in the most recent iteration of the course. Here, the red vertical line indicates the median. In response to this question, students were guided to respond on a scale from 1 to 5, where 1 was “What’s Python?” and 5 was “I could teach an intro Python Class!” How comfortable are you with programming in Python? There have also been a number of logistical changes across iterations however, for Spring 2020, the largest logistical changes were that I 1) did not require/motivate attendance at any specific time, 2) exams were completed remotely and were open notes/open Google and 3) coding labs were graded on effort rather than simply “showing up”.

Cogs 18 ucsd how to#

Further, I have included more demonstrations of common issues in code that students encounter and demonstrated more explicitly how to refactor and improve code style. I increased the live coding I’ve done throughout the course with a particular focus on doing so toward the end of the course. While the structure of the course has remained consistent, having learned from where students struggled previously, I’ve changed the time I dedicate to certain topics and the way in which I explain many things, particularly in the last few weeks of the course when we move away from Jupyter Notebooks and discuss code testing, documentation, and code style.









Cogs 18 ucsd