{"id":5612,"date":"2015-09-13T09:00:14","date_gmt":"2015-09-13T15:00:14","guid":{"rendered":"http:\/\/minkhollow.ca\/beckerblog\/?p=5612"},"modified":"2015-09-13T08:54:30","modified_gmt":"2015-09-13T14:54:30","slug":"worth-a-read-computer-science-courses-that-dont-exist-but-should","status":"publish","type":"post","link":"http:\/\/minkhollow.ca\/beckerblog\/2015\/09\/13\/worth-a-read-computer-science-courses-that-dont-exist-but-should\/","title":{"rendered":"Worth a Read: Computer Science Courses that Don’t Exist, But Should"},"content":{"rendered":"Approximate Reading Time: <\/span> < 1<\/span> minute<\/span><\/span>

\"CT23\"A list by\u00a0James Hague:<\/p>\n

CSCI 2100: Unlearning Object-Oriented Programming<\/b>
\nDiscover how to create and use variables that aren’t inside of an object hierarchy. Learn about “functions,” which are like methods but more generally useful. Prerequisite: Any course that used the term “abstract base class.”<\/p>\n

CSCI 3300: Classical Software Studies<\/b>
\nDiscuss and dissect historically significant products, including VisiCalc, AppleWorks, Robot Odyssey, Zork, and MacPaint. Emphases are on user interface and creativity fostered by hardware limitations.<\/p>\n

CSCI 4020: Writing Fast Code in Slow Languages<\/b>
\nAnalyze performance at a high level, writing interpreted Python that matches or beats typical C++ code while being less fragile and more fun to work with.<\/p>\n

CSCI 2170: User Experience of Command Line Tools<\/b>
\nAn introduction to UX principles as applied to command line programs designed as class projects. Core focus is on output relevance, readability, and minimization. UNIX “ls” tool is a case study in excessive command line switches.<\/p>\n

PSYC 4410: Obsessions of the Programmer Mind<\/b>
\nIdentify and understand tangential topics that software developers frequently fixate on: code formatting, taxonomy, type systems, splitting projects into too many files. Includes detailed study of knee-jerk criticism when exposed to unfamiliar systems.<\/p><\/blockquote>\n

There might be a few I’d add : like one about debugging, one on tool use (programmers should be made to use the tools they make), and maybe one about failed projects and code. What about you?<\/p>\n

Source: Computer Science Courses that Don’t Exist, But Should<\/a><\/em><\/p>\n