User Tools

Site Tools


haas:fall2017:discrete:projects

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:fall2017:discrete:projects [2017/09/23 13:09] – [Week 6] wedgehaas:fall2017:discrete:projects [2017/11/13 16:01] (current) – [Week 11] wedge
Line 22: Line 22:
 |  [[/haas/fall2017/discrete/projects/wpf4|wpf4]] (20170920)  | |  [[/haas/fall2017/discrete/projects/wpf4|wpf4]] (20170920)  |
 |  [[/haas/fall2017/common/projects/wcp|wcp5]] (20170923)  | |  [[/haas/fall2017/common/projects/wcp|wcp5]] (20170923)  |
-|  @lightgreen:[[/haas/fall2017/discrete/projects/pnc2|pnc2]] <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc2/faq|faq]]<nowiki>]</nowiki> <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc2/metrics|metrics]]<nowiki>]</nowiki> (20170927) +|  [[/haas/fall2017/discrete/projects/pnc2|pnc2]] <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc2/faq|faq]]<nowiki>]</nowiki> <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc2/metrics|metrics]]<nowiki>]</nowiki> (20170927) 
-|  @lightgreen:[[/haas/fall2017/discrete/projects/wpf5|wpf5]] (20170927) +|  [[/haas/fall2017/discrete/projects/wpf5|wpf5]] (20170927) 
-|  @lightgreen:[[/haas/fall2017/common/projects/wcp|wcp6]] (20170930)  |+|  [[/haas/fall2017/common/projects/wcp|wcp6]] (20170930)  |
 |  [[/haas/fall2017/discrete/projects/bdt0|bdt0]] (20171004)  | |  [[/haas/fall2017/discrete/projects/bdt0|bdt0]] (20171004)  |
 +|  [[/haas/fall2017/discrete/projects/wpf6|wpf6]] (20171004) 
 +|  [[/haas/fall2017/common/projects/wcp|wcp7]] (20171007) 
 +|  [[/haas/fall2017/discrete/projects/bdt1|bdt1]] (20171018) 
 +|  [[/haas/fall2017/discrete/projects/wpf7|wpf7]] (20171018) 
 +|  [[/haas/fall2017/discrete/projects/wpf8|wpf8 (BONUS)]] (20171018) 
 +|  [[/haas/fall2017/common/projects/wcp|wcp8]] (20171021) 
 +|  [[/haas/fall2017/discrete/projects/dcf2|dcf2]] (20171025) 
 +|  [[/haas/fall2017/discrete/projects/wpf9|wpf9]] (20171025) 
 +|  [[/haas/fall2017/common/projects/wcp|wcp9]] (20171028) 
 +|  [[/haas/fall2017/discrete/projects/pnc3|pnc3]] <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc3/faq|faq]]<nowiki>]</nowiki> <nowiki>[</nowiki>[[/haas/fall2017/discrete/projects/pnc3/metrics|metrics]]<nowiki>]</nowiki> (20171101) 
 +|  [[/haas/fall2017/discrete/projects/wpfA|wpfA]] (20171101) 
 +|  [[/haas/fall2017/common/projects/wcp|wcpA]] (20171104) 
 +|  [[/haas/fall2017/discrete/projects/nbm0|nbm0]] (20171108) 
 +|  [[/haas/fall2017/discrete/projects/wpfB|wpfB]] (20171108) 
 +|  [[/haas/fall2017/common/projects/wcp|wcpB]] (20171111) 
 +|  @lightgreen:[[/haas/fall2017/discrete/projects/yol0|yol0]] (20171115) 
 +|  @lightgreen:[[/haas/fall2017/discrete/projects/wpfC|wpfC]] (20171115) 
 +|  @lightgreen:[[/haas/fall2017/common/projects/wcp|wcpC]] (20171118)  |
 ======Class Stats====== ======Class Stats======
   * [[/haas/fall2017/discrete/projects/status|status]]   * [[/haas/fall2017/discrete/projects/status|status]]
  
 +
 +======Week 12======
 +  * Unveiling the EoCE this week; more fun and adventure awaits!
 +
 +======Week 11======
 +  * Focusing on different approaches to problem solutions in the next project, **yol0**
 +
 +======Week 10======
 +  * We've touched on different number bases through interacting with various projects. Now, we will be specifically focusing on them.
 +
 +======Week 9======
 +  * Our last foray into primes with a new twist: one loop for central processing.
 +
 +======Week 8======
 +  * And now with a new debugging tool in hand (via **bdt1**), we can commence on our next dcf exploration, with the **dcf2** project.
 +
 +======Break 1======
 +  * The week 7 journal entry will be your bonus break week entry. You'll have until Thursday of break week to modify it, at which point I'll roll it to week 8 (which will be a normal weekly entry- our journal entries will now sync up with the week!). If you don't touch week 7 it won't harm you, it will only help you if you contribute any content.
 +  * We've switched over to the new lab46 system. Still testing functionality, most things seem to work out of the box. Be sure to run the **fixmail** script on lab46 to reset configurations for the new setup.
 +
 +======Week 7======
 +  * Some good progress being made by some on **bdt0**, turns out to be an even better algorithmic exploration than I had planned. Again, only beneficial if you've been immersing yourself in it.
 +  * Knowledge assessment in class on Thursday.
 +  * http://tuxnes.sourceforge.net/gamegenie.html
 +    * Bonus discrete project, write an encode/decoder for NES game genie codes
  
 ======Week 6====== ======Week 6======
Line 35: Line 77:
   * Perhaps pointless, but I am starting to feel like a //broken record//...   * Perhaps pointless, but I am starting to feel like a //broken record//...
     * for those unfamiliar with that anachronistic saying (or its origins), it refers to a side effect of listening to non-digital music media with physical defects (specifically referring to vinyl records with scratches). As the playback mechanism relies upon tracing along the surface, various physical deformities could jump or skip the record, at times resulting in the same sequence being repeated over and over again. Compact Discs with scratches could also suffer from this, especially in certain poorly-implemented digital buffering scenarios.     * for those unfamiliar with that anachronistic saying (or its origins), it refers to a side effect of listening to non-digital music media with physical defects (specifically referring to vinyl records with scratches). As the playback mechanism relies upon tracing along the surface, various physical deformities could jump or skip the record, at times resulting in the same sequence being repeated over and over again. Compact Discs with scratches could also suffer from this, especially in certain poorly-implemented digital buffering scenarios.
-    * I find myself expending energy and resources dispensing advice and help, only to continually experience it falling on deaf ears. Or, perhaps more aptly, going in one ear and out the other, lacking that requisite sticking in the ear sponge that lies between. And certainly not universally... there are those who regularly do listen and benefit. I am not speaking about them. But those who **continually** experience the same troubles, be it from lack of discipline (procrastination, poor time management, brute forcing, etc.) or just in general avoiding proper planning and brainstorming.+    * I find myself expending energy and resources dispensing advice and help, only to continually experience it falling on deaf ears. Or, perhaps more aptly, going in one ear and out the other, lacking that requisite sticking in the ear sponge that lies between. And certainly not universally... there are those who regularly ask questions and who do listen and benefit. I am not speaking about them (they are wonderful, and if anything I'd like more questions). But those who **continually** experience the same troubles, be it from lack of discipline (procrastination, poor time management, brute forcing, etc.) or just in general avoiding proper planning and brainstorming.
       * When I exert, in good faith, effort to help, giving some useful suggestions and even explaining some concepts, only to be prompted later with a question clearly devoid that anything meaningful was obtained from the prior exchange, it is disheartening.       * When I exert, in good faith, effort to help, giving some useful suggestions and even explaining some concepts, only to be prompted later with a question clearly devoid that anything meaningful was obtained from the prior exchange, it is disheartening.
-      * When I see, time after time, people seeking "help" on how to get past their current hurdle, appealing to mercy and the altruistic charity of others, getting nothing from the experience (because they run into the exact same problems the next hop down the road), it is disheartening.+      * When I see, time after time, people seeking "help" on how to get past their current hurdle, appealing to mercy and the altruistic charity of others, yet getting nothing from the experience (because they run into the exact same problems the next hop down the road), it is disheartening.
       * When I observe people avoiding challenging things, perhaps due to inadequate learning in past experiences, sacrificing current growth, and thereby keeping them static and limited: it is disheartening.       * When I observe people avoiding challenging things, perhaps due to inadequate learning in past experiences, sacrificing current growth, and thereby keeping them static and limited: it is disheartening.
       * Yet when I see those who are taking advantage of what I am saying, ARE taking away something from interactions, AND diving into new and unexplored things (perhaps even being challenged, but clearly learning and growing from the experience), that IS quite heartening.       * Yet when I see those who are taking advantage of what I am saying, ARE taking away something from interactions, AND diving into new and unexplored things (perhaps even being challenged, but clearly learning and growing from the experience), that IS quite heartening.
-        * The problem, of course, is when there seems to be a small yet constant group who fits this latter category (of demonstrating proficiency and learning and understanding), in motion greatly advancing from their former states to ever-expanding new states of comprehension and capability, and a somewhat larger group who are insistent (consciously or otherwise) to remain exactly where they are. +        * The problem, of course, is when there seems to be a small yet constant group who fits this latter category (of demonstrating proficiency and learning and understanding), in motion greatly advancing from their former states to ever-expanding new states of comprehension and capability, and a somewhat larger group who are insistent (consciously or otherwise) to remain exactly where they are, doing things the way they are used to doing them
-          * There's a difference between having difficulty assembling a solid compound logical condition vs. having difficulty laying down proper syntax for an **if()** statement.+          * There's a difference between having difficulty assembling a solid compound logical condition based on what one thinks is going on vs. having difficulty laying down proper syntax for an **if()** statement in general.
           * There's a difference between needing a second pair of eyes to run through one's logic following deep and thoughtful planning, vs. running into a conceptual wall trying to code first without actually knowing how to do the task at hand.           * There's a difference between needing a second pair of eyes to run through one's logic following deep and thoughtful planning, vs. running into a conceptual wall trying to code first without actually knowing how to do the task at hand.
-          * There's a difference between accidentally using **strlen()/strcpy()/strcmp()** with binary data based on a conceptual misunderstanding, and those trying to shoehorn in using the same functions to make their code work because they heard others were using it, and are looking upon it as a magic panacea.+          * There's a difference between accidentally using **strlen()/strcpy()/strcmp()** with binary data based on a conceptual misunderstanding, and those trying to shoehorn in using the same functions to make their code work because they heard others were using it, and are looking upon it as a magic panacea (so these people neither understand why their code isn't working, nor why these functions may be a bad idea).
     * There's a short-term and long-term operation at play here:     * There's a short-term and long-term operation at play here:
       * The short-term represents the individual projects we encounter each week, milestones on our journey from start to completion of our semester's journey.       * The short-term represents the individual projects we encounter each week, milestones on our journey from start to completion of our semester's journey.
Line 50: Line 92:
         * When you are hired/tasked to develop on some project, it isn't going to be for single, one-shot, little programs. It will likely be for some long-running and evolving project. The pnc and dcf projects are an attempt to acclimate you to that evolving attribute of problems. Where you don't just solve it and drop it, but must continually revisit, revise, expand, enhance. Having a long-term view of where things are going and your strategies for approaching them.         * When you are hired/tasked to develop on some project, it isn't going to be for single, one-shot, little programs. It will likely be for some long-running and evolving project. The pnc and dcf projects are an attempt to acclimate you to that evolving attribute of problems. Where you don't just solve it and drop it, but must continually revisit, revise, expand, enhance. Having a long-term view of where things are going and your strategies for approaching them.
         * Yet far too many are still stuck in their short-term, brute-forcing ways. And in that desperation I see things like over-helping (getting access to code or solutions that the person does not truly understand, aside from "it works!!1!") and people driving themselves to exhaustion.         * Yet far too many are still stuck in their short-term, brute-forcing ways. And in that desperation I see things like over-helping (getting access to code or solutions that the person does not truly understand, aside from "it works!!1!") and people driving themselves to exhaustion.
 +        * Those who are adequately on the long term train are noticing some great things:
 +          * intrinsic limitations to current implementation, and often ask me questions on this (and frequently receive bonus points for their insightful demonstration of understanding).
 +          * perceptions that the later things are actually getting simpler/easier (again, these things haven't gotten that way, but the individual's understanding has facilitated implementation).
 +          * the projects, far from being annoying, frustrating, or painful, are actually fun, if not more than a little addicting. That is because, through understanding, they are not just seeing the implementation-specific details in front of them, but a broader impact on how they approach their solution, even applying that forward to contemplating how their solution would hold up to future project scopes/constraints.
 +          * more tangible, but: they start on them well in advance of the deadline. These are the people racking up bonus points, and if anything, are putting the finishing touches on things as the deadline looms, vs. fretting over why their code still won't compile, or has serious logic errors.
     * So I have to ask:     * So I have to ask:
       * Is discrete really all that hard?       * Is discrete really all that hard?
       * Is discrete the problem?       * Is discrete the problem?
-      * I'm only trying to show you insights into the things you will be experiencing (ie taking a "you have to be this high to ride the ride" approach) in the future. If you are struggling, constantly, and with basic things (due to lack of planning and discipline-- I mean, things happen. That's different than procrastination and needing constant hand-outs to get by each checkpoint), is that really something external to you? Or is it you? Yes, discrete tends to be more conceptually involved, but if you're not putting in the investment to properly grapple with these conceptual interactions, discrete will be more than just hard, it will be downright exhausting and impossible.+      * I'm only trying to show you insights into the things you will be experiencing (ie taking a "you have to be this high to ride the ride" approach) in the future. If you are struggling, constantly, and with basic things (due to lack of planning and discipline-- I mean, things happen. That's different than procrastination and needing constant hand-outs to get by each checkpoint), is that really something external to you? Or is it you? Yes, discrete tends to be more conceptually involved, but if you're not putting in the investment to properly grapple with these conceptual interactions, discrete will be more than just hard, it will not only remain challenging, but it will become downright exhausting and impossible.
     * With that said, while those on track continue to grow, expand, and impress, there are some making excellent progress to transition from being hopelessly overwhelmed to getting nicely on track to benefit from the experience. I just wish, in total, it represented more than a minimal majority (if that).     * With that said, while those on track continue to grow, expand, and impress, there are some making excellent progress to transition from being hopelessly overwhelmed to getting nicely on track to benefit from the experience. I just wish, in total, it represented more than a minimal majority (if that).
-      * If you're clinging on for dear life **BECAUSE FINANCIAL AID**, you really want to rethink what you're doing. Discrete is but a mild taste of what is to come.+      * If you're clinging on for dear life **BECAUSE FINANCIAL AID** or because you've not thought your long-term plans through, you really want to rethink what you're doing. Discrete is but a mild taste of what is to come. And not from me so much as transfer school or job. Encountering things you've never specifically encountered before yet have to work with it.
       * Just saying "I should have paid more attention in the prior class" is NOT a solution. It is a small admission of the problem. Far too many seem to think that admitting they blew a previous chance is somehow a "get out of jail free card". But think about it, how does admitting "I know what my problem is- I don't know how to program!" turn into "can I have my A now?" It does not compute.       * Just saying "I should have paid more attention in the prior class" is NOT a solution. It is a small admission of the problem. Far too many seem to think that admitting they blew a previous chance is somehow a "get out of jail free card". But think about it, how does admitting "I know what my problem is- I don't know how to program!" turn into "can I have my A now?" It does not compute.
         * Some have said they'd like to re-take CPROG, perhaps even next semester. But there's a logical flaw in that: If you feel you could tangibly benefit from retaking CPROG in the future, how is that helping you NOW, when you're clearly deficient in the necessary basics for success in discrete? Hint: it is not.         * Some have said they'd like to re-take CPROG, perhaps even next semester. But there's a logical flaw in that: If you feel you could tangibly benefit from retaking CPROG in the future, how is that helping you NOW, when you're clearly deficient in the necessary basics for success in discrete? Hint: it is not.
-        * More than a few people have stated they'd like to sit in on my CPROG class, yet to date a scant few have seemed to seriously follow-through (and those that have, I have considerable optimism regarding their success). And by seriously follow-through, to be both physically AND MENTALLY present, actually learning and picking up important basics.+        * More than a few people have stated they'd like to sit in on my CPROG class, yet to date a scant few have seemed to seriously follow-through (and those that have, I have considerable optimism regarding their success, both in the present and near future, but also further into the future as well- they are demonstrating their ability to make a sound investment in their future). And by seriously follow-through, to be both physically AND MENTALLY present, actually learning and picking up important basics.
  
 ======Week 5====== ======Week 5======
haas/fall2017/discrete/projects.1506172151.txt.gz · Last modified: by wedge