8 ms·
How I'd teach computer science
- bryanp 10y agoSo go teach CS :-)
- omaranto 10y agoSounds like a cool course, not sure I'd call it computer science, though.
- deeebug 10y agoThis doesn't sound like a Computer Science course. Maybe for something like a Software Engineering degree, but not for CS.
- ASpring 10y agoAgreed. The post is so devoid of any context about where this would fit in a program that it's hard to tell what the author was attempting to convey. It's absolutely inappropriate as a starting point for either CS or SE.
- catnaroek 10y agoAgreed. This raises even more questions: Do we need more computer scientists or software engineers? Why do so many universities offer computer science programs, if the job market is primarily asking for software engineers? Even worse, why do so many universities offer software engineering programs that call themselves “computer science” programs? Isn't that lying to students?
- ktRolster 10y agoThe job market seems to favor Computers Science degrees over Software Engineering degrees. Although it favors job experience over both.
- catnaroek 10y agoWhy? Because of the word “scientist” in the degree's name? What exactly is the point to employing a scientist to perform non-scientific tasks?
- deanstag 10y agoMy guess would be that a CS program would cover more fundamentals on which you can always build upon, but a Sw Engineering program might not focus on the basics as much. Of course there might be exceptions in either programs.
- ktRolster 10y agoI think because CS degrees tend to produce more competent programmers, for some reason.
- wyager 10y agoBecause CS endows a more fundamental understanding than SE. SE classes are often along the lines of "Here's how you do OOP in Java", whereas CS classes are more along the lines of "Here's how you formalize OO semantics and then implement the semantics at a low level." The latter approach is generally more effective, if more difficult.
- catnaroek 10y agoSometimes I'm not even sure if “software engineering” can be said to exist as a discipline. In every other branch of engineering (mechanical, chemical, etc.), practitioners actually understand the scientific foundations of their profession, even if they aren't research scientists themselves.
- protomyth 10y agoI would actually like to see a study on that. I'm not so sure its true, and it certainly has not been my experience. I do wonder if anyone is ever going to do a full study on the subject. Weirdly, some of the best programmers I have met are people who go their degree in Music Theory. Odd and really not enough sample size.
- deleted 10y ago[deleted]
- arekkas 10y agoThat's what you do in courses like "Introduction to Software Engineering" (first/second lecture), which usually are part of the first BSc CS semester. I don't disagree though that the title is misleading and the content quite disappointing and it wouldn't make a semester-long course because that list is covered in 10 minutes and it's nowhere near academia.
- catnaroek 10y agoI knew what to expect from the title. An actual computer scientist wouldn't be clueless enough to suggest (s)he can teach everything about computer science. Instead he would probably say how (s)he would teach something in his(er) narrow field of specialization - algorithms, databases, operating systems, compilers, whatever.
- empath75 10y agoIt's not even software engineering, it's just basic troubleshooting skills. You could teach automotive repair or plumbing the same way, probably. I'd like to see a course taught in that that doesn't necessarily focus on computers, because those skills are tremendously applicable in pretty much every field.
- ktRolster 10y agoWriting bug reports took me 5 minutes to figure out how to do in the real world (or maybe an hour, or even a day, but not too long). This is not something you need to take a class to figure out.
- k2xl 10y agoI don't think writing bug reports is as simple as it seems. Sometimes it actually takes time (and experience) to learn how to communicate an issue them properly. Writing steps to reproduce, which systems, etc
- bsder 10y ago> I don't think writing bug reports is as simple as it seems. Only because most CS students have never taken a real laboratory course. If you get a hard-nosed lab teacher, you figure out real quick all the information required to reproduce your results. And it's remarkable how much you have to record and how detailed you have to be. The best lab teachers are the ones who will flunk your assignment if they can't reproduce your results from your lab notebook.
- ktRolster 10y ago"A minute to learn, a lifetime to master." Seriously though, do you feel you missed out because your CS degree didn't teach you how to write bug reports? I mean, really?
- k2xl 10y agoI didn't personally, but I do think introducing more software development processes into the curriculum would've been beneficial.
- micahbright 10y agoSounds like a Software Engineering course. Probably want to add in the rest of Computer Science if you really want to teach Computer Science though.
- ktRolster 10y agoSeems like a good start for a class. If he keeps it up, and does a lot more work, he'll end up with a good program.
- primitivesuave 10y ago"Computer science is no more about computers than astronomy is about telescopes." (Edser Dijkstra) Computer science is the study of algorithms - what is described here may be best described as software engineering. As an educator who has been involved in computer science education for almost a decade, I find the code-centric approach described here to be counterproductive.
- catnaroek 10y agoAlgorithms are one big part of computer science, of course. But there's more than that. Computer science is also about abstraction: how to organize our programs so that they can be understood (not just tested!) with the minimum amount of intellectual effort possible. Dijkstra himself wrote a lot about this topic: https://www.cs.utexas.edu/users/EWD/transcriptions/EWD02xx/EWD288.html https://www.cs.utexas.edu/users/EWD/transcriptions/EWD02xx/E... https://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/EWD303.html https://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/E... https://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/EWD393.html https://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/E...
- primitivesuave 10y agoI absolutely agree with your point that abstraction is a fundamental idea of computer science, but I believe it still falls more in the conceptual realm of computer science than in the practical realm of software engineering. For example, if I were to describe abstraction to a student, I may first get them to imagine building a factory assembly line. Instead of thinking about the assembly line as a whole, I would encourage them to think about each stage of the assembly line, and how to test each individual machine separately. By abstracting each step of the solution and making it easy to verify its correctness, they can achieve the minimum intellectual effort in testing the entire solution as you described. Thank you for taking the time to add the EWD links, I'm sure others reading this thread will find them as enlightening as I do.
- throwaway729 10y agoIt's not counter-productive at all, as long as your goal is to teach Software Engineering. And every course of study in Computer Science should have at least a semester's worth of content on Software Engineering. But it's also important to remember that Software Engineering is not Computer Science. Also, a 4-year-long course of study in Software Engineering should definitely cover things aside from coding. Some Computer Science for sure, but also the basics of business, ethics, economics, politics, psychology, and so on.
- bmh100 10y agoWhile there are people commenting on how the techniques sound a lot like a software engineering class, as opposed to a computer science class, I think this approach overall would be fantastic for computer science. Writing tests and documentation are great discipline for assignments. Once these software engineering practices are in place, they can serve as a framework for future assignments. The HTTP server as a starting point is an excellent idea. This allows for students to see the results of their efforts in an interactive, visual, tangible way. Successfully implementing a search algorithm for the first time is great, but how much more rewarding would it be to see an unsorted list on a web page, a "sort" button", and watching the list sort before your eyes? Students become trained in one of the most underrated skills in software: communication. They also gain practice in building prototypes to help with job hunting or demonstrating to managers. Does this reframe the curriculum in the context of industry rather than academia? Yes, but I feel it would be incorrect to orient CS around the minority of students who will pursue academic careers anyway.
- wyager 10y agoThis is "code monkeying", not "computer science". A valuable skill, to be sure, but let's not mix terms.
- lazyant 10y ago(Besides this not being "CS" as people are pointing out) This is good to give some ideas to people that like to tinker and learn by themselves, who are the people needing instructions the least. The thing is, if students don't have a step-by-step instructions they will fail and complaint, you can tell the author is not a teacher. Anecdote time: I did MS in CS in an university in the US, in one course we had to set up some XML web service in Java, the prof lifted all the instructions from official web site and gave us the slides with step-by-step commands but he missed one step, so next week nobody except me (who bothered to look up the error and RTFM) had the service set up, this was a 500 or 600 level course.
- zintinio5 10y agoYou've laid out a plan to teach software development. Computer Science might be more accurately named "Computing Science".
- bsder 10y agoSpoken like someone who hasn't taught a CS class. You really want to teach some useful skills and not actually disrupt your CS class too much? Here's the start. Lecture 1: How to drive a basic IDE (I used to choose Eclipse, but I might rethink that nowadays depending on language used. One of the IntelliJ projects might be easier.). Most students are stunned at the difference between what they use as an editor vs what an IDE can do. Once somebody shows them what is possible, they start swimming really well. Lecture 2: Source control and automated testing. For most students, they view this as a homework dropbox that checks and runs their work. That's good enough to start. Some of them progress beyond this. NOW, I can actually start to talk about the substance of my class as well as how to put that in programs. Guess what? I have to give these lectures to every single class I teach. It doesn't matter if the class is 101 or 499, every single class.
- gravypod 10y agoI've been pushing the head of the class I help TA for to make it mandatory that students use PyCharm. He's still afraid that PyCharm will intimidate the users but I think it's well worth it. We have 2nd and 3rd year students at my college who still haven't opened Eclipse, IntellJ/PyCharm/Whaterver else, or even Visual Studios. They have also never used a debugger. They have no idea what formatting standards, or naming standards are. It's crazy.
- bsder 10y ago> I've been pushing the head of the class I help TA for to make it mandatory that students use PyCharm. He's still afraid that PyCharm will intimidate the users but I think it's well worth it. Dropping an IDE and automated testing into your class is not without cost. 10% of the questions the rest of the semester will be how to do something in the IDE. And, occasionally, you're not going to know the answer. Saying "I don't know" can be intimidating to someone who doesn't have 20+ years of experience. As for source control and automated testing--congratulations, you are now Mr. IT-guy for 30 people for the next 14 weeks. And students can be really creative in wedging their repositories. To this day, I still have no idea how one student managed to create a recursive repository in Subversion. You really have to be committed to accept the cost of the things I recommended.
- gravypod 10y agoI often hear many many people say "what you want is Software Engineering not Computer Science" and I'd say YES that's EXACTLY what I want. The problem is finding a university that will give it to you. In my opinion the field of Computer Science should be the study of abstractions, logic, derivation of algorithms, understanding the limits and possibilities of computer hardware, and programming (being the development of a real-world solution to a problem that can be run to process data). If it's not one of those items I don't think it belongs in Computer Science. Sadly, our field has been managed, since the beginning, by professors who think it's math field. That's the way I'd say most hiring managers look at it: Computer Science = Programmer. The only place this isn't paralleled is academia. So I'm perfectly fine with saying either everyone else is wrong and my definition is correct, in which case we need to seriously evaluate how Computer Science is taught in schools. Alternatively I'm wrong, in which case I'd love to attend a university that will allow me to get a bachelor's, master's, and maybe even a PhD in Software Engineering because the truth is I hate whatever it is that academia considers Computer Science but I love logic, creating solutions to problems, thinking about the limits of hardware, optimizations, and everything that goes along with it. Sadly I cannot find any university that offers this. My university offers a SE masters degree but it requires a BS in Computer Science! How ironic! But yea, I'm perfectly happy with either of those outcomes. The people who are, in my opinion wrong about what "Computer Science" is can stay in their corner and I'll stay in mine.
- bsder 10y ago> The problem is finding a university that will give it to you. Go find one of the multi-week intensive programming "camps" with a good reputation (do be careful--there's a lot of snake oil out there). That's what you want.
- sotojuan 10y agoThe problem is that bootcamps are 3 months of "intense" and pressured learning the most marketable language at the time and as far as I know aren't accredited like regular universities. What I'd like to see exist is a 1~ year program at a real college (can be community college!) that is basically a more comprehensive and relaxed[1] version of a bootcamp. [1] I don't mean this to sound "easy", just not 8-10~ a day of work like bootcamps are.
- mccolin 10y agoThis is applicable to an Intro to SOFTWARE ENGINEERING course. As an exercise. Not the primary content. It is not Computer Science.
- pbh101 10y agoThis is very close to the iteration loop I designed for the onboarding team I am currently running: I'm getting fresh CS grads and need to add the software engineering into their skillset. I can't say I'd really change up the status quo, though: I wouldn't substitute any of the time they spent on CS to be reduced to include more 'real-world' items: you can focus on those afterwards and they tend to be organization-specific. Give me folks with a solid theoretical foundation and I can work on their client-interaction and big-codebase-team-programming skills.