Programming is not for computers.
Programming is a form of self-expression reflecting the human behind the machine. Programming amplifies human intent. For better or for worse, the consequences of programming are vast in the internet age. We are truly programming the world: not only in the physical, IoT sense, but in affecting human behavior at every scale. Decisions affecting business, government, and daily life are made on the basis of data and algorithms. How should educators serve as responsible stewards of the future?
Microethics and the study of social implications provide a framework for understanding the impacts of these decisions. Programming focusing on the end product leads to narrow definitions of software quality. The new software engineering investigates the crucial but often understated development process and program lifecycle in terms of its broader effects on the world.
The goal of an introductory computing course (even one ostensibly about programming) should not be to produce better software engineers. Better software engineers are exactly what they sound like: “better software engineers.” Designing education as a pipeline is an incorrect metaphor on many levels, but it’s perhaps most saliently realized in how it reproduces the bias and inequity of the status quo.
We should instead strive to construct a new ethos for computer science through education: designed in collaboration with students, integrating intentional teamwork, empowering students as creators of technologies, exploring the equally technical and social boundaries of computing, situating computing as explicitly antiracist, and acknowledging that learning takes time—that students bring to the classroom diverse and differently valuable human experiences.
Critical programming language learning
The study of programming should involve exploring different forms of expression.
If programming in and of itself is a form of self-expression, then it is necessarily shaped by computing culture. Programming languages themselves are artifacts of this culture: features, functionality, and semantics change over time in response to programmer preferences. Organizations create their own subcultures and dialects in the form of project management processes, style guidelines, and common best practices. Programming and software engineering at large is a community of practice whose participants determine the norms of firstly what is and is not programming.
But computing culture concerns more than just programming. Computing culture is situated in a broader of context of the problems that it solves. Computational teamwork—intentional, integrative teamwork between both people and machines—is a critical component. How can we help students learn to “work effectively, efficiently, and ethically together” in hybrid teams of people and machines?
Coding is just one (algorithmic) way of communicating mathematical ideas. But just as important is the ability to communicate these ideas across a variety of media and to a variety of stakeholders: not only in the form of code reviews or technical papers, but also in the form of presentations, emails, tweets, blog posts, and videos. Communication occurs across various media for various recipients with various objectives. Computer programming is not only about coding, but also about reading, writing, and translating between languages and modalities to learn effective representations for programs.
Emergency remote teaching
But where are we today? In the transition to emergency remote teaching, our course is doing well thanks to deep investment in both human capital (undergraduate TAs) and technical capital (infrastructure for online learning). Incidentally, many of these suggestions were just published in the context of teaching an online discrete mathematics class by Sandy Irani and Kameryn Denaro (2020).
Considering these strengths and the importance of aligning learning objectives and learning activities, we’ve focused on redesigning the introductory programming course around just-in-time teaching and pair (or group) programming. Online courses benefit from additional points of contact with student, so we adapted best practices on Humanizing Online Teaching and Building Rapport to Improve Retention and Success in Online Classes. Teaching assistants have been pivotal in reaching students. Videos of the just-in-time teaching are recorded based on the discussions that we have in class. (Loom has been a great help in streamlining the entire process.)
For assessment, we dropped all high-stakes exams. Our weeklong programming assignments have typically had stringent anti-collaboration policies, so they’re now appropriately renamed “take-home assessments” reflecting their role in the curriculum. Two-stage quizzes with recovery and resubmission opportunities is an interesting but currently untested idea that will be implemented next time to reintroduce some of the assessment lost due to removing in-person exams. In the grand scheme of things, these are still mostly baby steps, but steps nonetheless, toward critical programming language learning.
As for pedagogy, I shared the following with students on the first day of class.
How learning works
Learning is a process that requires deliberate practice. There are four components to deliberate practice.
- Sustained motivation.
- Tasks that build on prior knowledge.
- Immediate, personalized feedback on tasks.
- Repetition of all of the above.
Each week in the course will introduce 2 or 3 lessons. Each lesson is designed around deliberate practice. You can expect each week in the course to roughly follow this schedule (time distribution in parentheses).
Before-class introduction (3 hours). Prepare your brain to maximize in-class learning by completing the lesson introduction before class. Optionally, watch the lecture video for additional context.
Lecture meetings (3 hours). Engage with your neighbors and the class on the ideas. Clarify questions from the lesson introduction. Seek help and seek to help others. Go beyond getting the correct answer.
Quiz section meetings (2 hours). Check your understanding applying the ideas in more complex situations. Master the lesson by working with TAs and peers.
All lessons will be completed in ed, our digital learning platform. Lecture videos and lesson content are also posted on the course website.. The course website has a powerful search bar to help you find and review lesson content.
A larger take-home assessment will be released at the end of each week. Assessments are submitted through Grade-It! and reviewed by your quiz section TA.
Take-home assessment (7 hours). Apply all of the ideas learned during the week into one big program. In addition to solving the problem (external correctness), assessments will also emphasize programming style (internal correctness).
To prepare for the work we will do in lecture meetings, instead of reading quizzes, each week you will create an external brain to help guide you to the most important information in each lesson. Each week’s external brain will be different, but they will most often involve highlighting details, synthesizing passages, and coming up with general steps for solving common programming problems.
External brains will be submitted through Gradescope. Submit a PDF document either typed or legibly handwritten. The goal of creating an external brain is to organize information in a way that is the most helpful for your learning, so pick the format that works best for you. There’s no such thing as one right way to make an external brain.
Stop and think: How does creating an external brain help us learn?
Each lesson contains a mix of reading, quiz questions, and coding challenges. Each of these are important opportunities for learning to occur. Make the most of your learning opportunity by reflecting critically on the following meta-questions as you work through the lesson.
- Why are we learning this?
- How does this new concept fit in with everything we know so far?
- Describe this concept in your own words.
- Summarize the code in terms of its purpose (not line-by-line).
- Give a general template or list of steps for solving programming problems of this type.
In addition, there will be stop and think questions like this one embedded within readings. These are good questions to ask and answer in your own words. Collaborate with other students to improve your external brain during each lesson.
We’ve taken special care to design the course such that all of the work can be done on your own time. However, personalized feedback is a key component of deliberate practice, so we’ll still hold online class sessions using UW Zoom Video Conferencing.
Online classes share the same norms as in-person classes. Participate from a quiet space where you can listen and speak. If you participate from a more public space, be sure you won’t be disturbed by others while there. When talking to others, participate with your camera (if you have one) turned on using horizontal (not vertical) video.
Tips for success
The university has a page on Tips for Success at the UW. Here are a few highlights that will be particularly important for online learning.
Maintain a regular schedule. Use a weekly planner or calendar to maintain a regular schedule. Set alarms and reminders before class meeting times. Build in routines such as getting out of bed and dressing for the day (even if you’re not going outside).
Take care of your body, mind, and soul. Exercise regularly, sleep 6–8 hours every night, and eat well. Studying online can be isolating, so keep up with friends and family as much as possible. Take advantage of opportunities to study with other students using video chat if possible.
Do not work on your bed. Humans make spatial associations, so it’s especially beneficial to set up a separate space that is dedicated only to study and work. Get oxygen flowing by maintaining a natural posture and incorporating movement such as walking.