13,420
edits
Changes
no edit summary
:* I also want to create some '''YouTube videos placed prior to the "Review Questions" section for''' '''"Connecting the Dots"''' so to speak. These would be short videos to provide reasons why they are using these tools. Especially LAB1!! Hint, Hint, (i.e. I don't want students to lose lab1!!!!)<br /><br />
:* Which lab (i.e. in relation to "fall lab line-up") would be affected by '''SysVInit -> Systemd''' ?<br /><br />
:* Strong agreement '''I am in STRONG AGREEMENT with "re-factoring" web pageswiki labs and course notes content. ''' I strongly believe in '''"forward" and "backward" linkages''' as well. Let's take a journey down a river (hopefully no waterfalls). In addition to preamble about what student will be performing, it would be nice to "tie-in" the previous lab to allow a "flow" ("end-to-end"). This would relate to a "forward linkage" of what students can expect in the next lab. I strongly believe that well designed courses provide a "flow". This is NOT to indicate "spoon-feeding", but a nice "fit" in a practical container (yet not too constrained). I like the steps listed in the "re-alignment".<br /><br />
::'''As a "follow-up" to this "flow":'''<br /><br />
::* For debugging, I would stress common problems that students have made in the past, and a general suggestion that the student take to remedy the situation. Careful "check-points" should be indicated (perhaps with a '''"check-point icon"''' to have students CAREFULLY confirm their contents with the suggested output, and then direct them to debugging. I would NOT recommend YouTube videos, since this is where the students would benefit most from "learning" and "calling over the instructor"...<br /><br />