User Tools

Site Tools


haas:spring2016:cprog:projects

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
haas:spring2016:cprog:projects [2015/11/10 13:15] – external edit 127.0.0.1haas:spring2016:cprog:projects [2016/04/13 12:19] (current) – [Week 11] wedge
Line 6: Line 6:
  
 ======Projects====== ======Projects======
-  * [[/haas/fall2015/cprog/projects/cci0|cci0]] (due 20150909+  * [[/haas/spring2016/cprog/projects/cci0|cci0]] (due 20160127
-  * [[/haas/fall2015/cprog/projects/mms0|mms0]] (due 20150916+  * [[/haas/spring2016/cprog/projects/mms0|mms0]] (due 20160203
-  * [[/haas/fall2015/cprog/projects/dow0|dow0]] (due 20150923+  * [[/haas/spring2016/cprog/projects/dow0|dow0]] (due 20160210
-  * [[/haas/fall2015/cprog/projects/mbe0|mbe0]] (due 20150930+  * [[/haas/spring2016/cprog/projects/mbe0|mbe0]] (due 20160224
-  * [[/haas/fall2015/cprog/projects/mbe1|mbe1]] (due 20151007+  * [[/haas/spring2016/cprog/projects/pnc0|pnc0]] (due 20160302
-  * [[/haas/fall2015/cprog/projects/cos0|cos0]] (due 20151028+  * [[/haas/spring2016/cprog/projects/mbe1|mbe1]] (due 20160309
-  * [[/haas/fall2015/cprog/projects/afn0|afn0]] (due 20151104+  * [[/haas/spring2016/cprog/projects/cos0|cos0]] (due 20160316
-  * [[/haas/fall2015/cprog/projects/sam0|sam0]] (due 20151111+  * [[/haas/spring2016/cprog/projects/sam0|sam0]] (due 20160323
-  * [[/haas/fall2015/cprog/projects/cbf0|cbf0]] (due 20151118)+  * [[/haas/spring2016/cprog/projects/cbf0|cbf0]] (due 20160406) 
 +  * [[/haas/spring2016/cprog/projects/afn0|afn0]] (due 20160413) 
 +  * [[/haas/spring2016/cprog/projects/gfo0|gfo0]] (due 20160420)
 ======Class Stats====== ======Class Stats======
-  * [[/haas/fall2015/cprog/projects/status|status]]+  * [[/haas/spring2016/cprog/projects/status|status]]
  
 ======Week 11====== ======Week 11======
-  * We will continue working on our digit classmoving ever closer to an eventual object-oriented project (but not quite yet) +  * We're into the second week of registration; I've already helped a few people... don't waitget this done sooner rather than later. 
-  * This week'project is related to **sam0**, only instead of encoding/decoding text using caesar cipher, your task in **cbf0** will be to unscramble an image file.+  * The next project**gfo0** is now available. 
 +  * We will not have class next Tuesday (April 19th2016). I will be away at 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====== ======Week 10======
-  * We will continue with our Object-Oriented endeavors this week, finishing up/reviewing classesand then moving on to inheritance+  * If you've heard a rumor that the fall 2016 schedule is available to view (not sign up formerely view), you are somewhat correct. However, you'll either note or be made aware that it is not updated for the computer courses
-    * The first Object-Oriented project may get underway+    * If you're one of those awesome pre-planners and want up-to-date information, you can pull up my correct schedule here: 
 +      * http://djdates.com/schedule/index.php?content=createschedule&ts=&ds=ALL_201710_Fall2016_WIP&c=instr&m=Haas%2C+Matthew 
 +        * you can probably hack that URL to pull up other computing instructor schedules 
 +        * updated schedules should be in MyCCC by Thursday.
  
 ======Week 9====== ======Week 9======
-  * We started on Object-Oriented Programming in C++ +  * Possibly starting on Object-Oriented Programming/C++ 
-  * Secret Agent Messaging (sam0is the new project+  * 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 "advance submission" bonus points due to its straddling of the week off. 
 +    * 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====== ======Week 8======
-  * I haven't heard a peep from anyone all break... hopefully that means lots of people are having fun drawing a circle of squares+  * We may play with files this week
-  * The next project to tide us over: another mental math trick. **afn0** makes for a great party trick. +  * **sam0** is the new project
- +  * Remember that these projects attempt to highlight the application of various important conceptsSkirting them not only disenfranchises you, but loses points! Of particular note: 
-======Break Week====== +    * loops facilitate/automate things. Do not write out each instance where loop will do, you'll not only lose points, but you'll have an egregiously massive program. 
-  * I evaluated mbe1! We are currently up-to-date on our projects. +    * a "circle" of squares implies 360 degreesThat'lot of points, so you probably don't want to manually calculate each oneYou'll want to use a loop! Do not just manually place squares in a circle-like arrangement- plot the squares in a circle via a loop where you are calculating the x, y coordinates for each of them.
-    * A bit of surprise to be sure... less than half the class submitted it. mbe1 was bit more involved, so I wonder if the outcome was due to expectational procrastinationLet this be a lesson to you for future projects. +
-  * I went and scoured through all the opii and updated any records I had. +
-  * Warning grades go out today... be advised.+
 ======Week 7====== ======Week 7======
-  * We should be wrapping up our initial discussion of functions, and then explore some C library stuffspecifically image creation/manipulation with gd+  * Exploring some librarieswriting programs that construct and generate images. 
 +  * Next project is **cos0** 
 +  * I evaluated **pnc0**... almost a 50/50 split between really getting it/exploring and not getting it/sub-bare minimum. Some just didn't conform to project specifications (especially with respect to output), some didn't seem to understand the process of computing a prime. 
 +    * Why did I not hear from anyone having trouble? I got a few good questionsbut from too few people considering the end results. 
 +    * If you got it working and your code wasn't to output specifications, did you not test it? That's why I wrote **primerun** (it wasn't just to race for best times). 
 +    * The further we go, the more abstract things will become. I hope you are testing/writing things out on paper, and not just trying to write out some code. Plan, and check!
  
 ======Week 6====== ======Week 6======
-  * We're starting to get to the point where the volume of concepts and coding possibilities at your disposal are considerable. The only way you will do well is if you take the time to play and review and otherwise expose yourself to the concepts and ideas that such things enable. Do not just come to class and type in whatever code we work on... you MUST tinker with things outside of class too. Experimentbreak things, try solving related problems. +  * Finishing up arraysthen onto structs or functions 
-  * Barring any questions, we'll be exploring functions this week, the last major concept to cover in C. Then, we'll take a little time exploring all these concepts in combination, before moving on to C++.+  * Next project is **mbe1** 
 ======Week 5====== ======Week 5======
-  * Week 5 hits a few milestones: +  * Arrays, and using loops to drive them. 
-    * This week effectively marks the 1/3 waypoint of the semester. Can you believe it? +  The next project is **pnc0**. 
-    * Fall begins on September 23at 4:21 A.M. ... so be sure to enjoy what remains of summer! +  * Something to take note of: http://www.johndcook.com/blog/2012/04/03/a-b-c/
-  * General observations: +
-    * rushing begets confusion and stalled progress. Be it rushing due to procrastination, or rushing due to not putting adequate amounts of time into understanding, it will hurt you if you do not spend the appropriate amount of time to learn the new concepts and to become increasingly fluent with them. +
-    I cannot stress this enough: **you must take the time to practice this material**.+
 ======Week 4====== ======Week 4======
-  * Our programming capabilities grow with each passing class, each passing week. +  * Likely getting to loops this week, possibly touch on arrays. 
-  * Barring any questions, we'll be proceeding onto to loops this week+  * The next project, **mbe0**, has been released.
-    * for() - counting (aka "automatic counter") loops +
-    * while() - top driven relational loops +
-    * do while() - bottom driven relational loops +
-  * arithmetic shortcuts: +
-    ++ - increment by 1 (comes in both pre- and post-increment varieties) +
-    -- - decrement by 1 (comes in both pre- and post-increment varieties) +
-    += - increment by provided value +
-    -=*=, /=, %=+
  
 ======Week 3====== ======Week 3======
-  * We explored: +  * We should be getting into selection statements this week (if()/switch()). 
-    * pointers +  The next project, **dow0**, has been released.
-    * negative numbers +
-    * if statements +
-      * else if +
-      else +
-      compound if statements +
-      relational operators +
-      and how properly organizing them can be beneficial +
-    * viewed assembly conversion of our C programs (-S argument to gcc) +
-    binary maskslogic+
  
 ======Week 2====== ======Week 2======
-  * Explored input with scanf() +  * To continue our experience with C, you will be undertaking the first of the mental math projects this week, **mms**. 
-  * Expressed values according to different schemes (octalsigned/unsigned decimalhex, ASCII) +  * Be sure to take time to play with what you've learned outside of class. 
-  * Started looking at pointers, including double pointers+  * We'll continue our exploration of variablestypesand their properties. 
 +  * And give an intro on performing input and output using C standard library functions.
  
 ======Week 1====== ======Week 1======
-  * Welcome! I've wrapped all the initial activities into one project, **[[/haas/fall2015/cprog/projects/cci0|cci0]]**, that I'd like you to perform by the given deadline (by 11:59:59pm / 23:59:59).+  * Welcome! I've wrapped all the initial activities into one project, **[[/haas/spring2016/cprog/projects/cci0|cci0]]**, that I'd like you to perform by the given deadline (by 11:59:59pm / 23:59:59).
   * Get familiar with logging into the pod systems, and once there:   * Get familiar with logging into the pod systems, and once there:
     * open up a terminal     * open up a terminal
haas/spring2016/cprog/projects.1447161350.txt.gz · Last modified: 2016/01/18 22:13 (external edit)