3 ms·
So I actually took this class in 2018. Unfortunately I don’t think it’s good enough just yet. CS 193 was a very low effort class (1cr), where you could follow
by kritr 5y ago
So I actually took this class in 2018. Unfortunately I don’t think it’s good enough just yet.
CS 193 was a very low effort class (1cr), where you could follow the command by command instructions and perform all the tasks necessary to pass.
Unfortunately tools like git, vim, and shells all possess philosophies and concepts that are very hard to grasp without context, and constant use.
We were on multiple occasions told the mantra, add-commit-push, which I will say is enough for basic git usage, but since pretty much none of the subsequent classes used git to any capacity, I would assume many students lost all familiarity within the next semester (Makefiles that automatically git added and pushed code were used for submitting code).
I also think most people were hindered by vim, lacking sufficient instruction but still being presented it as the primary option.
I think if you’re going to implement a similar class / program, the tools really have to have uptake beyond a single course.
Sidenote, the different shell types weren’t covered in my semester, we just used bash / dash.
- austinl 5y agoThat’s interesting (and definitely unsurprising) to hear! I think freshman year might be a bit too early to appreciate the curriculum, before students have seen how ubiquitous some of these tools are in engineering jobs. Maybe it would be better spread out over time. I think the trade-off on timing here is with internships during the summer after freshman year. I think you’ll have a much better chance of success if you’re at least roughly familiar with these workflows vs. interns who are totally unfamiliar with version control systems, for example. And perhaps that’s all the course is meant to accomplish at 1cr.