MIT 6.00 Intro Computer Science (OCW)
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
Read the readings, practice the examples shown in the readings, watch the lecture videos, read the Python Tutorial in the documentation - and practice the examples shown there, do the problem sets, ask questions here
Thanks for the help, I look forward to talking with in the future and present! Thanks again!
What I would suggest for you is to read the "Overview" and "Session Activity" to get a sense of what the professor wants to teach you. -Jot down the terms in the description of the session and look out of them during the lecture. If you don't understand what he's explaining, try to use alternative sources that explain that same term. I find wikipedia does a pretty good job, just search using a good query (e.i [Term in question] +computer science). Or try getting book at the library, go through the Index for the term. -Try to answer the "Check yourself" questions. -Lastly, do the "Problem Sets" Note: Don't forget to download the "Resources", they contain the Source Code you need for the Session. Take Care and May the force be with you!
IMO, one of the most important skills for a programmer to develop, and develop the patience to follow through, is problem decomposition. You'll learn the term later, it just means breaking down a problem into smaller problems called subproblems. The patience part is to then break the subproblems down, and break those down, however many times until your code kind of writes itself.
I'm brand new too, but the combination of lectures, recitations, and assignments seems to be working well. I'm up to lecture 6 and currently working through the Scrabble game problem. So far, when I watch the lectures, I keep a notepad open and type notes to help me remember. I've also watched some parts more than once to try to understand better. I print out the sheets of code that go along with the lectures, and makes notes next to the examples shown there. With the code, I've been writing a couple lines at a time and then printing test statements. It's helped me see right away if I'm doing something wrong. Once I get a section done I sometimes have to go back and delete a dozen or so print statements. So far, I'm having fun though. Getting it right is like solving a puzzle, but more satisfying. Best of luck!