CodeTriage VS missing-semester

3. Open Source Contribution

I wrote a book with a chapter on how to write docs for other people’s code https://howtoopensource.dev

I also wrote an open source tool for writing and testing tutorials https://github.com/zombocom/rundoc and another that will email you undocumented methods of open source code so you can practice writing documentation https://www.codetriage.com/.

CodeTriage helps you contribute to open source by “picking a handful of open issues and delivering them directly to your inbox”. (Source: CodeTriage)

Here are open source projects listed https://www.codetriage.com/ You can filter for "C".

The biggest untaped potential (IMHO) is not one company funding 1 full time maintainer, but EVERY company allowing and encouraging EVERY developer to help and work with open source. This was the basis of my web app https://www.codetriage.com/. I have a chapter on it in my book How to Open Source (https://howtoopensource.dev/), and I talked to Yehuda about it for about an hour after my last talk at Philly ETE.

You can also use websites like up-for-grabs, goodfirstissue, or CodeTriage to find projects with open issues. Find one that looks easy or interesting to you and comment on it, asking if you can take a shot at it.

I recommend these resources to help you contribute https://www.codetriage.com/ (free) and https://howtoopensource.dev/ (paid). DM if you can’t afford a copy.

The missing semester of your cs education

https://missing.csail.mit.edu/

You mentioned having issues with accessory concepts so perhaps this might help: https://missing.csail.mit.edu/. There's also a chapter on git

https://missing.csail.mit.edu/ is a good way to pass the Dec-Jan break if you want to prep for CS2030S + some more general stuff.

Reflecting a little bit more I don't think it was replit's fault, per-say. But that change should have been made together with a larger adjustment to the program. Like adding a class/unit in the style of [the missing semester](https://missing.csail.mit.edu/) to make sure people came away with a good range of intuitions.

From MJD's post: I think CS curricula should have a class that focuses specifically on these issues, on the matter of how do you actually write software?

But they never do.

FWIW, MIT's "The Missing Semester of Your CS Education" attempts to deal with this lack, though, even there, it's an unofficial course taught between terms, during MIT's IAP -- Independent Activities Period[1] -- and not an actual CS course.

[0] https://missing.csail.mit.edu/

[1] https://en.wikipedia.org/wiki/Traditions_and_student_activit...

Link to the "missing semester of your CS degree" course by MIT.

Rightly called The Missing Semester (of Your CS Education), this class from MIT will teach you how to use some of the tools that are fundamental to the software engineering ecosystem. From shell scripting to the fundamentals of information security—spanning around 12 lectures—you can add a bunch of practical skills to your toolbox.