Group items tagged

given leadership positions while remaining in the classroom for their entire careers.

If we continue to treat our teachers like children, what will become of our children?

I quit teaching because I was tired of feeling powerless. Tired of watching would-be professionals treated as children, infantilized into silence. Tired of the machine that turns art into artifice for the sake of test scores. Tired of being belittled, disrespected and looked down upon by lawyers, politicians, and decision-makers who see teaching as the province of provincials, the work of housewives that can be done by anyone.

Old vendor relationships may no longer be as critical, and you might end up dealing with anyone from Amazon to Apple, players who only recently began to play in the enterprise space.

We also know that there are plenty of low- to no-cost learning options available to people on a daily basis, from books on nearly every academic topic at the local library and on-the-job experience, to the television programming on the National Geographic, History and Discovery channels. If learning can and does take place everywhere, there has to be a specific reason that people would be willing to spend tens of thousands of dollars and several years of their life to get it from one particular source like a college. There is, of course, and again it’s the credential, because no matter how many years I spend diligently tuned to the History Channel, I’m simply not going to get a job as a high-school history teacher with “television watching” as the core of my resume, even if I both learned and retained far more information than I ever could have in a series of college history classes.

High School students are sitting passively and listening during approximately 90% of their classes.

For younger students, I think that the ability to make something professional-looking, like a real grown-up would, is paramount.  Sadly, I think this means that LOGO and BASIC aren't much use any more*.

So, we have a few choices.  You can try to write phone apps that look just like real phone apps, design interactive websites that look just like real interactive websites, or do something with embedded systems / robotics.  Avoid the temptation to make these things into group projects; the main thing every student needs to experience is the process of writing code, running it, debugging it, and watching the machine react to every command.

It is important to consider what an 11 to 18-year old is familiar with in terms of mathematics and logical thinking. An average 11-year old is probably learning about fractions, simple cartesian geometry, the concept of units, and mathematical expressions. By 15, the average student will be taking algebra, and hopefully will have the all-important concept of variables under his/her belt. So much in CS is dependent on solid understanding that symbols and tokens can represent abstract concepts, values, or algorithms. Without it, it's still possible to teach CS, but it must be done in a very different way (see Scratch).

At this point, concepts such as variables, parenthesis matching, and functions (of the mathematical variety) are within easy reach. Concepts like parameter passing, strings and collections, and program flow should be teachable. More advanced concepts such as recursion, references and pointers, certain data structures, and big-O may be very difficult to teach without first going through some more foundational math.

The key is that the concepts in CS aren't just there for the hell of it. Everything was motivated by a real problem, and few things are more satisfying than fixing something you really want to work with a cool technique or concept you just learned.

"Are we allowed to use ideas from our writing exercise to help us write this paper?" she asked. "Of course," I said. "That was the whole point of the writing exercise—to get you a head start in thinking about how you want to approach your paper." "OK," she said. And then after a brief pause: "Because at orientation they told us we weren't allowed to use our own work twice." "Ah," I said. "That doesn't really apply in this case. And anyway, I don't really mind, in this course, if you take a paper that you've written for another course and revise it for an assignment in here. You just have to make sure that what you turn in fulfills my specific assignment. Other professors might feel differently, though. So I would always ask before you tried to do that."

So why deprive our students of the opportunity to learn those same lessons, by recycling a particular paper from one course to the next?

I can foresee one more objection: What's to prevent a student from recycling the same paper from course to course to course? Students who did so would lose the valuable opportunity to practice their writing—and writing, like any other intellectual or physical skill, requires lots of practice. But—practically speaking—the opportunity to reuse a paper might arise only once or twice in a student's career, thanks to the diversity of our course assignments and disciplines.