haas:fall2017:discrete:projects
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:fall2017:discrete:projects [2017/09/15 12:48] – [Week 5] wedge | haas:fall2017:discrete:projects [2017/11/13 16:01] (current) – [Week 11] wedge | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| ======Projects====== | ======Projects====== | ||
| - | * [[/ | + | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| - | | + | | |
| + | | [[/ | ||
| + | | | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | [[/ | ||
| + | | @lightgreen: | ||
| + | | @lightgreen: | ||
| + | | @lightgreen: | ||
| ======Class Stats====== | ======Class Stats====== | ||
| * [[/ | * [[/ | ||
| + | |||
| + | ======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, | ||
| + | |||
| + | ======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, | ||
| + | |||
| + | ======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:// | ||
| + | * Bonus discrete project, write an encode/ | ||
| + | |||
| + | ======Week 6====== | ||
| + | * I am thinking I'd like to have a Knowledge Assessment, sometime next week, likely on Thursday, focusing on your ability to critically think and solve a problem, based on experiences and concepts we've been dealing with in the course so far. | ||
| + | * 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. | ||
| + | * 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, | ||
| + | * 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 " | ||
| + | * When I observe people avoiding challenging things, perhaps due to inadequate learning in past experiences, | ||
| + | * Yet when I see those who are taking advantage of what I am saying, ARE taking away something from interactions, | ||
| + | * 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), | ||
| + | * There' | ||
| + | * There' | ||
| + | * There' | ||
| + | * There' | ||
| + | * The short-term represents the individual projects we encounter each week, milestones on our journey from start to completion of our semester' | ||
| + | * The long-term represents the collective experience and growth obtained through the overall process. Recognizing shortcomings in an initial approach, learning from the mistake, and then demonstrating increased awareness and capability because of it. | ||
| + | * Again, not universally, | ||
| + | * When you are hired/ | ||
| + | * 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!" | ||
| + | * Those who are adequately on the long term train are noticing some great things: | ||
| + | * intrinsic limitations to current implementation, | ||
| + | * perceptions that the later things are actually getting simpler/ | ||
| + | * the projects, far from being annoying, frustrating, | ||
| + | * 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: | ||
| + | * Is discrete really all that hard? | ||
| + | * 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), | ||
| + | * 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** 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!" | ||
| + | * Some have said they'd like to re-take CPROG, perhaps even next semester. But there' | ||
| + | * 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, | ||
| ======Week 5====== | ======Week 5====== | ||
| + | * 09/21 @ 8:10am: updated **check** script in **dcf1**. Do a **make getdata** to grab a copy. | ||
| + | * And then there was pnc1.. some continued to demonstrate their excellence and understanding, | ||
| * I continue to be impressed by various interactions- some great insights gained, questions asked, realizations had. That is what the core purpose of discrete is all about- fostering thinking. So for those who have been (and even finding the thinking increasingly addicting): keep up the good work. | * I continue to be impressed by various interactions- some great insights gained, questions asked, realizations had. That is what the core purpose of discrete is all about- fostering thinking. So for those who have been (and even finding the thinking increasingly addicting): keep up the good work. | ||
| * As I had mentioned in reference to knowledge I encountered during my polyphasic sleep research, cannabis (marijuana, weed, etc.) DOES impact sleep (and not in a beneficial way): | * As I had mentioned in reference to knowledge I encountered during my polyphasic sleep research, cannabis (marijuana, weed, etc.) DOES impact sleep (and not in a beneficial way): | ||
haas/fall2017/discrete/projects.1505479715.txt.gz · Last modified: by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
