8 ms·
CS101: Introduction to Computing Principles
- triska 4y agoThe impression I get from this schedule is that this is a collection of quite ad hoc topics that are in some cases quite far removed from what I expected to see covered in a course that is intended to introduce computing principles. For instance, are "For Loops", "If Statements" and "Spreadsheets" really essential to computing, can these concepts be considered "computing principles"? What about logic? I note there is a reference to "Boolean Logic" as one part of the "Spreadsheets and Data" lecture. What about models of computing, or defining what we even mean when we say "computing"? The lecture notes hint at some of these topics in the final lecture ("Theory and Conclusions"), almost like an afterthought.
- zasdffaa 4y agoI agree it's weird, but as someone with a decent CS background... > What about models of computing, or defining what we even mean when we say "computing"? ... I found all I've learn is worth nearly nothing in industry. Which saddens me and it shouldn't be, but it is so. Really basic principles get useful but only in very high-end areas, stuff that I can barely comprehend (eg. automata for model checkers etc).
- ascar 4y ago> I found all I've learn is worth nearly nothing in industry It really depends what you work on. Doesn't even have to be high end. When working on performance critical code I was glad about my computer science and math education more than once. And performance can get interesting even at a few million users or regardless of user-count in realtime applications. When writing business logic without performance and scalability in mind, yea, all that knowledge remains dormant. Reality is that there is simply far more business logic work out there than performance critical code.
- zasdffaa 4y agoAll my understanding of perf-critical code has come from understanding of the usual - pathological cases for algorithms, memory layout, cache friendliness etc. etc. None of that except perhaps a very little of the first, came from my formal education, it's all been down to me reading up on stuff. Can you give me an idea of what your CS & maths education gave you that you found so useful for tuning code? Maybe I'm missing something important.
- ascar 4y ago> algorithms, memory layout, cache friendliness all of this was an integral part of my formal education. Algorithms and datastructures and complexity analysis was mandatory in the undergraduate studies, the lower-level stuff mostly in elective postgraduate classes of my computer science program. From the top of my head also things like operating systems, compilers, networking, vectorization (SIMD), instruction pipelining, branch prediction, threading, NUMA, thread-pinning/affinity that help understanding how my code is actually executed. On the math side set theory, probability theory and analysis also came in handy more than once. Linear algebra I guess if I had to deal with matrices, which is probably relevant in the AI/machine learning fields (not my area of expertise). All of my math education was mandatory undergraduate classes. Sure, it's well established that you don't need formal education to learn all these things (which applies to most fields, not just CS), but they are certainly part of computer science and taught as part of formal education at I would assume most good universities. From my experience (which is Germany and Japan, not the US) especially postgraduate degrees are what you make of them. You can learn nothing relevant for performance critical engineering or you can learn a ton.
- zasdffaa 4y ago>> algorithms, memory layout, cache friendliness > all of this was an integral part of my formal education. Other than algos, we got none of this. > the lower-level stuff mostly in elective postgraduate classes of my computer science program. From the top of my head also things like operating systems, compilers, networking, vectorization (SIMD), instruction pipelining, branch prediction, threading, NUMA, thread-pinning/affinity that help understanding how my code is actually executed. We got compilers. Otherwise none of this - in fact these are not computer science by some definitions. It was pretty much maths at the end. I don't think we were well served in some ways. > which is Germany and Japan, not the US I'm in the UK.
- feet 4y agoWhich part of the industry do you work in?
- zasdffaa 4y agoIT contractor. Much of it DB stuff. The range of work you do goes from 'sit here and scrub data' to being given a free-ish rein when you've proven yourself, and then you can be very creative. It's all business-oriented work, as in, we need this ASAP. I'd like to do more research-oriented work, or at least cutting edge. Something that's solving longer term business problems, not just 'get it done yesterday'.
- rst 4y agoIt's a first course in programming, with occasional glances at other relevant topics, whatever the title. MIT tried to do an intro course which was actually an introduction to principles, but the effect was so harsh that undergrads without previous background in programming were often advised to take a more conventional "intro to programming" couse first. The textbook, "Structure and Interpretation of Computer Programs", is still available -- but the course is no longer taught at MIT, after they decided it was no longer serving the needs of the students.
- drc500free 4y agoThank you for giving me a flashback to 20 years ago, realizing that I couldn't perform in 6.170 because I didn't know Java but there were no Course 6 classes that taught Java.
- NavinF 4y ago> What about models of computing, or defining what we even mean when we say "computing"? IMO starting with that is the worst possible way to introduce CS to students who are (statistically) far more interested in programming and software engineering than in CS. Hell, most students in this class are probably there only because it’s a prereq for the class they actually want to take.
- UncleMeat 4y agoIn my experience, the huge majority of people who take an intro CS class want to learn how to solve problems with programs and to learn how other people solve problems with programs. At Stanford, almost every single undergrad takes an intro CS class but only a fraction of those go on to major in CS or get a job in software. You've got one class to provide useful information to people - teaching people about models of computation or set theory is not going to capture people's interest or help them meaningfully in the future. But if somebody says "hey, I know enough python to figure out how to split up a huge PDF into individual files, one for each page, then suddenly they are empowered to solve problems. Same reason we wait until Real Analysis to teach delta-epsilon limits while the engineers are off taking PDEs.
- cinntaile 4y ago> Same reason we wait until Real Analysis to teach delta-epsilon limits while the engineers are off taking PDEs. This is very country dependent, we were taught delta-epsilon limits in high school. Maybe not with the same depth, I don't know.
- indymike 4y agoIf you look at the "lecture notes", yes it seems ad hoc. After looking through some of the readings, I think this is a fantastic, very comprehensive survey class.
- rjsw 4y agoI remember finding out that a Biology major taking an "Introduction to Computing" course had still not touched the keyboard after six weeks. If a course like this helps people without a programming background get started then that seems good to me.
- khaki54 4y agoThis course looks "fine"; however, I would recommend that anyone interested in exploring CS (or perhaps even if you are a self-taught and very able coder who wants to learn those missing fundamentals ) takes CS50 out of Harvard. It is easily the most engaging course I have ever taken and it's available for free on edx.org or you can take the "real" class from Harvard extension for a couple grand. You can go into this class as an underwater basket weaver or a strong coder and get a ton out of it.
- toinewx 4y agocan you elaborate on why it is that good? why is it so engaging?
- jstx1 4y agoWell selected material and great quality of teaching. It's for complete beginners and it's very accessible without being dumbed down in any way.
- khaki54 4y agoFor me, they teach the fundamental (basic) concepts and then have you cycle through a bunch of programming languages week to week to reinforce they are simply the tool and they all have their own pros and cons. When I took it, they had javascript, c, python, php, java, snap, integrating APIs and libs... maybe more. The course has 2 tracks which are graded the same: "regular" for those new to cs/programming and "hacker" which has a bit more of a challenge to keep it interesting, and you just do whatever one you want to do that week. Each assignment has additional optional material explaining and reinforcing the concept so if you are a little opaque in an area you can go and study that a bit more before returning to the assignment. Ultimately, there is a walkthrough for each week that gives you about 95%+ of the answer in case you get really stuck. If you understood the concept well enough from the lecture or your own background, you can just blast right through the assignment, or put your own spin on it. Supposedly this course is responsible for hundreds (if not thousands) of people changing their planned field of study to be more technical due to the huge accessibility of the material to what they call "less comfortable" students. They also teach you a few adjacent things that are relevant and probably wouldn't be covered by most modern programming courses. They teach you how to use desktop VMs for your IDE. They teach you how to use a basic IDE. They teach you the basics of Linux command line. They teach you what memory leaks are and how to find them. You're graded on style, there is an automated style checker. For me, I got a kick out of all the sorting algorithms and how it applied to big O notation and software complexity. Previously I understood roughly how it worked but the course went deep enough where I tried implementing some of them on my own "for fun" to see if I could do it. For my final project, I built a native android app, and although they didn't teach anything specifically about mobile app design, I had enough confidence at that point to knock it out. On top of all those items, production value of the course seemed huge, very well done.
- oxff 4y agoIt's a weird porridge of topics. Just do this instead: https://dcic-world.org/ https://dcic-world.org/
- molticrystal 4y agoWhen a person completes week 4, they'll have learned boolean logic, if/for loops, bytes & variables, and had an overview of hardware from the previous weeks. If the person is ambitious, that is the minimum required to begin, and it might be worth seeing just how far they can get in Nand2Tetris[0] where a person simulates building elementary logic gates and circuits leading to an also very basic Arithmetic logic unit and simple ram from nand gates. I wouldn't expect the person with just a few weeks of CS101 to do week 4 of Nand2Tetris where they try out machine language on their machine that leads to building an assembler, and then a compiler, as this eventually requires knowing Java or a similar language, but more power to them if they preview the course and see how much they can understand. [0] https://www.nand2tetris.org/ https://www.nand2tetris.org/
- deleted 4y ago[deleted]
- photochemsyn 4y agoThis looks like a very practical course that introduces a lot of tools/concepts valuable for any student in any field relying on the modern computational setup. However, actually learning programming however is just a time-consuming effort and there's no real way around it. There's a whole industry built around 'we can teach you programming in ten weeks' or whatever and it's all nonsense. Some years ago I was working full-time in a molecular biology lab, and part of the job involved using a lot of computational bioinformatics tools. I knew a couple of CS people who were writing bioinformatics software and they showed me pages of code, and I asked "realistically, how long would it take me to learn to write these kinds of programs" and the answer was always "at least two years of full-time effort" (It was mostly C code they were working with at the time, plus Java for the user interfaces). My personal experience finally learning to program over the past few years is right in line with those estimates. There aren't really any shortcuts, you just have to put in the hours of work, week after week, month after month, year after year. As with most fields, a lot of the introductory material is outdated for modern industry but since the more advanced technology relies on an understanding of the basics, you can't just leapfrog it, that's like trying to learn calculus without ever taking any algebra, or trying to grok CRISPR without knowing how basic DNA replication works.
- Arisaka1 4y agoNot that I disagree with you but I don't see what the course is promising as anything close to what you juts described and rant about, and neither does it claim that it won't take time. Were you perhaps attempting to respond to someone else's comment?
- jdcampolargo 4y agoThis is better plus you learn programming https://www.learncs.online/ https://www.learncs.online/
- deleted 4y ago[deleted]
- troupe 4y agoI'd highly recommend looking at the edX course "How to Code: Simple Data" and "How to Code: Complex Data" as an introduction to computer science. Those two classes were created around a solid pedagogy of how students learn to break real world problems down into code. Dr. Kiczales is incredibly good at taking everything step by step and making sure nothing gets left out or missed.
- gorgoiler 4y agoAre functions part of the course? Functions are both extremely practical for real world problems where code is repeated but with different values, as well as of course being fundamental to the theory of computation. I very much enjoy introducing my pupils to functions. It is the first time they really get to use the computer as a tool for accelerating their abilities. Up until then, their code has utility in the order of how much they wrote. Functions can let you write a page of code that does so much more.
- no_time 4y agoHow hard does it get later on? This looks very tame and quite fun. In comparison, here in Hungary our "Basic computer science" was filled to the brim with graph theory and was absolutely joyless.
- steve76 4y ago
- nightski 4y agoIt is much more programming specific focused, but I still think my favorite intro to programming course ever is the original 1986 Structure & Interpretation [1]. [1] https://www.youtube.com/playlist?list=PLE18841CABEA24090 https://www.youtube.com/playlist?list=PLE18841CABEA24090
- opnitro 4y agoFlagging my two favorite introductions to computing: How To Design Programs: [https://htdp.org https://htdp.org] A Data-Centric Introduction to Computing: [https://dcic-world.org https://dcic-world.org]
- vo2maxer 4y agoGreat suggestions. Thank you.
- xwdv 4y agoWhat I ultimately came to realize about all computer science is that all problems are basically figuring out how you will do 3 steps: 1. Organize data 2. Transform the data according to some input. 3. Output a result. Once you’ve very clearly mapped out your data structures, everything else becomes fairly trivial. Functions are nothing more than turning data from one form into another. Outputs are just data in some new structure that can be easily consumed for some other purpose. I challenge anyone to find a problem that doesn’t fit this formula.
- deleted 4y ago[deleted]
- orsenthil 4y agoAfter learning programming, practicing with leetcode is a good way to learn Computer Science. It will cover Algorithms, System Design and Databases.
- israrkhan 4y agoI like the course, but more than the course I like various recommendation in this post. This is best part of HN.
- cardy31 4y agoThis has already been mentioned, but I can’t recommend CS50 highly enough. It literally changed my life. I was doing a music degree and ran into CS50 on Reddit somewhere and decided to give it a shot. Long story short I ended up getting a CS degree and working for a large tech company.
- SneakyTornado29 4y agoBTW this is not the intro stanford cs course. Take CS 106A! It is the best intro to CS I've ever seen. This course is like AP CS Principles whereas CS 106A is like AP CS A.
- john1633 4y agoThere is an error on the 16th slide of the second lecture: XOR only returns true when the inputs are not the same. (https://web.stanford.edu/class/cs101/lecture02.html#/16 https://web.stanford.edu/class/cs101/lecture02.html#/16)