Live data from Hacker News

Computer science courses that don't exist, but should (2015)

prog21.dadgum.com

11–20 of 308 posts

Re: Computer science courses that don't exist, but should (2015)

#12

The Classical Software Studies would be quite useful. Go write a game in 64kb of RAM in BASIC. It would really stretch your creativity and coding skills.

Agreed, it would be very interesting to see some of the care taken for resource management that is lost now because every machine has “enough” RAM and cycles…

Re: Computer science courses that don't exist, but should (2015)

#13
post #11

"CSCI 4020: Writing Fast Code in Slow Languages" does exist, at least in the book form. Teach algorithmic complexity theory in slowest possible language like VB or Ruby. Then demonstrate how O(N) in Ruby trumps O(N^2) in C++.

The book in question:

https://www.amazon.ca/Visual-Basic-Algorithms-Ready-Run/dp/0...

Re: Computer science courses that don't exist, but should (2015)

#14
post #3

Where’s the course on managing your reaction when the client starts moving the goal posts on a project that you didn’t specify well enough (or at all), because you’re a young eager developer without any scars yet?

That's the job of a (good) manager.

Re: Computer science courses that don't exist, but should (2015)

#16
post #9

It is interesting that no software engineering or computer science course I’ve seen has ever spent any time on CI/CD. Jenkins, Docker, Kubernetes, none of these sorts of things - and I don’t even mean these specific technologies, but moreover nothing even in their ballpark.

Personally it felt quite natural once you start to work on real software projects.

Re: Computer science courses that don't exist, but should (2015)

#17

The Classical Software Studies would be quite useful. Go write a game in 64kb of RAM in BASIC. It would really stretch your creativity and coding skills.

I’m e long thought the Gameboy Advance would make a great educational platform. Literally every aspect of the hardware is memory mapped. Just stuff values into structs at hard-coded addresses and stuff happens. No need for any OS or any API at all.

Re: Computer science courses that don't exist, but should (2015)

#19
The TFA wants the following computer science courses:

Unlearning Object-Oriented Programming: a course on specific software engineering techniques

Classical Software Studies: a course on the history of software tools

Writing Fast Code in Slow Languages: a course on specific engineering techniques

User Experience of Command Line Tools: an engineering design course

Obsessions of the Programmer Mind: course about engineering conventions and tools.

One day, the name of science will not be so besmirched.

Re: Computer science courses that don't exist, but should (2015)

#20
>CSCI 2100: Unlearning Object-Oriented Programming Discover 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."

This is just a common meme that often comes from ignorance, or a strawman of what OOP is.

>CSCI 4020: Writing Fast Code in Slow Languages Analyze 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.

I like this one, but see?

Python is heavily OOP, everything is an object in python for example.

I'm wondering if OP took a basic OOP course or would otherwise be interested in taking one? You can learn about a thing you are against, or even form your opinion after actually learning about it.

>

Post reply on HN