This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2016:cprog:projects [2016/02/01 17:00] – [Projects] wedge | haas:spring2016:cprog:projects [2016/04/13 12:19] (current) – [Week 11] wedge | ||
---|---|---|---|
Line 9: | Line 9: | ||
* [[/ | * [[/ | ||
* [[/ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
+ | * [[/ | ||
======Class Stats====== | ======Class Stats====== | ||
* [[/ | * [[/ | ||
+ | |||
+ | ======Week 11====== | ||
+ | * We're into the second week of registration; | ||
+ | * The next project, **gfo0** is now available. | ||
+ | * We will not have class next Tuesday (April 19th, 2016). I will be away at a conference (just for that day). | ||
+ | * We've been exploring Inheritance and Classes. | ||
+ | * There was a bug in my **flattenstatus** script; if you ran it before 8:20am on Wednesday, April 13th, then you may have incorrect data. Re-run it to generate a fresh and correct copy. | ||
+ | |||
+ | ======Week 10====== | ||
+ | * If you've heard a rumor that the fall 2016 schedule is available to view (not sign up for, merely view), you are somewhat correct. However, you'll either note or be made aware that it is not updated for the computer courses. | ||
+ | * If you're one of those awesome pre-planners and want up-to-date information, | ||
+ | * http:// | ||
+ | * you can probably hack that URL to pull up other computing instructor schedules | ||
+ | * updated schedules should be in MyCCC by Thursday. | ||
+ | |||
+ | ======Week 9====== | ||
+ | * Possibly starting on Object-Oriented Programming/ | ||
+ | * Unless there are questions... | ||
+ | * The next project is **cbf0**, which has us exploring the fascinating realm of binary data from the programmatic perspective. | ||
+ | * Two bonus point opportunities exist: | ||
+ | * more " | ||
+ | * if you make an opus entry before next Tuesday (March 29th), and another before the following Tuesday (April 5th), I will count one as an extra Opus entry (a great way to make up for any missed entries!) | ||
+ | |||
+ | ======Week 8====== | ||
+ | * We may play with files this week. | ||
+ | * **sam0** is the new project. | ||
+ | * Remember that these projects attempt to highlight the application of various important concepts. Skirting them not only disenfranchises you, but loses points! Of particular note: | ||
+ | * loops facilitate/ | ||
+ | * a " | ||
+ | ======Week 7====== | ||
+ | * Exploring some libraries, writing programs that construct and generate images. | ||
+ | * Next project is **cos0** | ||
+ | * I evaluated **pnc0**... almost a 50/50 split between really getting it/ | ||
+ | * Why did I not hear from anyone having trouble? I got a few good questions, but from too few people considering the end results. | ||
+ | * If you got it working and your code wasn't to output specifications, | ||
+ | * The further we go, the more abstract things will become. I hope you are testing/ | ||
+ | |||
+ | ======Week 6====== | ||
+ | * Finishing up arrays, then onto structs or functions | ||
+ | * Next project is **mbe1** | ||
+ | |||
+ | ======Week 5====== | ||
+ | * Arrays, and using loops to drive them. | ||
+ | * The next project is **pnc0**. | ||
+ | * Something to take note of: http:// | ||
+ | ======Week 4====== | ||
+ | * Likely getting to loops this week, possibly touch on arrays. | ||
+ | * The next project, **mbe0**, has been released. | ||
+ | |||
+ | ======Week 3====== | ||
+ | * We should be getting into selection statements this week (if()/ | ||
+ | * The next project, **dow0**, has been released. | ||
======Week 2====== | ======Week 2====== |