<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>educaction on C'est la Z</title><link>https://cestlaz.github.io/cestlaz-old-hugo.github.io/tags/educaction/</link><description>C'est la Z (educaction)</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 26 Jan 2019 16:06:08 -0400</lastBuildDate><atom:link href="https://cestlaz.github.io/cestlaz-old-hugo.github.io/tags/educaction/rss.xml" rel="self" type="application/rss"/><item><title>Sequencing Topics</title><link>https://cestlaz.github.io/cestlaz-old-hugo.github.io/post/sequencing-topics/</link><pubDate>Sat, 26 Jan 2019 16:06:08 -0400</pubDate><guid>https://cestlaz.github.io/cestlaz-old-hugo.github.io/post/sequencing-topics/</guid><description>&lt;p>
Monday&amp;#39;s the start of the Spring semester. Other than the 8:00am start
I&amp;#39;m looking forward to it. My 8:00am class is the honors/lab component
that goes with CS1. I taught it last semester and during each of the
past two years at Hunter. My second class is the follow up - more OOP
/ C++, data structures and some algorithms.&lt;/p>
&lt;p>
The material is old hat. I&amp;#39;ve taught it in Java more times than I can
count and also in C++ albeit many years ago. What&amp;#39;s new is that I&amp;#39;m
teaching my Hunter kids and I&amp;#39;m doing it in a college framework - two
days a week, 1:15 a session. I&amp;#39;m not thinking too much about how I&amp;#39;ll
teach each class - I usually figure that out in the moment - not
actually in the class but week to week based on the flow of the
class. &lt;/p>
&lt;p>
Right now, I have to make final decisions on sequencing, at least for
the start of the class. We got ahead of the game by covering most of
the C++ topics - inheritance, templates, overloading etc. at the end
of last semester so that
leaves all the data structures, algorithms, dynamic structures, and
memory management, recursion, and sorting and searching. If I have
time I&amp;#39;d also love to get into some graph stuff. &lt;/p>
&lt;p>
Here&amp;#39;s the plan, at lest for now.&lt;/p>
&lt;p>
We&amp;#39;ll start with recursion. They had the basics last term but now
we&amp;#39;ll talk about search - I usually focus this around a maze
solver. After this we&amp;#39;ll place recursion on hold - at least in terms
of class time and move to linked lists and dynamic memory. We&amp;#39;ll
follow this with sorting. The idea is that students have trouble
getting comfortable with both recursion and also with dynamic
structures first time through. Rather than ploughing through from
recursion to the recursive sorts I&amp;#39;m hoping that putting the dynamic
lists in between will give recursion some time to marinate in the
background. Likewise I&amp;#39;m hoping that the dynamic memory stuff can
marinate through the sorting unit for when we revisit it with stacks,
queues, and trees after sorting.&lt;/p>
&lt;p>
I don&amp;#39;t know if this is the optimal way of sequencing the topics but I
think it will work pretty well.&lt;/p>
&lt;p>
We&amp;#39;ll see as the semester progresses. If things are going swimmingly I
can always call an audible.&lt;/p></description></item></channel></rss>