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.
It's going good. A couple of questions. 1. How much code should we write. For example if im asked to find the square root of 10, should I write code that the user inputs any number and the code checks to make sure it is a number etc. Or is it just something that may be a good habit to get into? 2. Should I do all the optional questions. I havent done y je second one from week 2 as time was limited last week?
It's going good. I need to catch up on the reading but have done the exercises and homework and cracking on with the week 3 codeacademy stuff @jtb1979 I'd say, it's not a race. If you want to finish the week 2 exercise then go ahead. I found the optional exercises were more focused on making you think about *how* to program something, so I found that I made errors/bugs which helped reinforce knowledge I had perhaps skimmed over in the practical session and missed the significance of. That said, if an exercise asked me to calculate a sqrt, I'd take the quickest way to that unless it specifically wanted an all-singing all-dancing user interface
That's what im wondering. Do I go the quickest route and think "well i'm doing as asked". Or do I think "maybe they want me to do a little bit extra". I have seen examples on here that take a question and write 20 - 30 lines of code, where they are checking for errors and making sure it works with any input. Where my code is less than 10 lines and does exactly what is asked with no bells and whistles. I think what im asking really is what would a professor running the course expect?
@jtb1979 I think you have to let your heart be your guide. If you do more, you're going to learn more. It seems to me (a relative newbie) that all it takes to learn this stuff is practice. The more you practice, the better. I think you have to treat yourself like the professor. Do you give yourself a C for doing average work, or do you give yourself an A for completing the assignment. I have to admit, I'm in a similar boat. I've been pretty excited to complete the exercises, and haven't always gone back to make them as robust as I know they could be. Maybe it's a good challenge from here on out: complete the assignments, then see how you can make your answers better. Then we can give ourselves A+s (and probably learn a heck of a lot more).
It's going quite well. We have a local group of Mechanical MOOCers where I work that meets in a computer lab once per week to discuss Codecademy exercises and other aspects of the MOOC. There's also a group of Codecademy moderators who are taking the MOOC together. There are multiple venues for discussing the content, namely here in OpenStudy, our groups of 40, and the Codecademy Q&A forums. I think a good way to take the Mechanical MOOC is to do it immersively - just dive in and use all the resources that are available to get as much Python as possible out of it. The freedom from having to be concerned about grades or academic credits (and especially tuition!) is liberating.
I'm busy with the Week2 tasks.I enjoyed the Codecademy excercises!
Not too bad.