O'Really?

July 11, 2023

Amplifying student voices on employability with audio podcast interviews

How can we get better at listening to student voices to improve teaching and learning in our Universities?

This post summarises a talk I gave at the inaugural ITL Teaching & Learning conference at the Pendulum Hotel in Manchester on July 6th 2023 tackling this question. It describes recording and publishing twelve interviews with undergraduate Computer Science students shown in figure 1 on their personal journey from student to professional. The interviews are available as an audio podcast called Hearing your Future.

Figure 1: Twelve student voices from the last twelve months, interviewed and broadcast in twelve podcast episodes. From top left, Raluca, Jason, Brian, Carmen, Sneha, Alice, Jason, Ivo, Ingy, Nadine, Pedro and Amish. Portraits re-used from LinkedIn and Github with students permission.

According to Stephen Fry, “education is the sum of what students teach each other between lectures and seminars”. A more teacher-centric view of education would claim the opposite to be true, that education is primarily about what teachers teach their students, not what students teach other. Here’s how this old-school, chalk-and-talk view of education works: In lectures, seminars, labs and tutorials, teachers share their knowledge and expertise with students. While the Professors profess their monologues, the lecturers lecture, the educators educate, the teachers teach and the students study. Learners learn by watching, listening, reading and acting on the voices of their educators. Students are then examined, grades are given and that, in a nutshell, should be what the sum of education is. No?

The reality of course, is that education should be much more of a dialogue, a two-way conversation between students and teachers, rather than an expert-driven monologue to a passive audience. Both sides of this conversation need to be heard and in some cases, the student voices in these conversations can make valuable contributions, by co-creating curricula.

All too often the student voice gets drowned out in the busy noise of pedagogy. The demands of teaching in higher education mean that staff don’t always sufficient time and resources to listen, especially when teaching classes of hundreds of students with many ongoing conversations. In this blog post, I’ll explain how you can amplify some important student voices in these conversations using audio podcasting. I’ll describe some of the costs and benefits of recording and publishing these conversations so that more people can hear and learn from these voices, not just students but their employers and their educators too.

Student voices on employability

Student voices are particularly important when it comes to employability: enabling undergraduates to develop the professional skills that are essential to the workplace. I’ve been teaching professional skills and employability to Computer Science students for the last ten years at the University of Manchester. During this time, I’ve learned that there are many different voices and opinions that need to be heard. Which of these voices, written or spoken, do students pay attention to most? Is it:

  • ❌ The voices of their employability tutors?
  • ❌ The voices of their Professors and lecturers?
  • ❌ The voices of their careers service consultants and advisors?
  • ❌ The voices of employers and alumni?
  • ❌ The voices of their friends and family?

These voices all have their own influence, but in my experience, there’s one voice that is listened to above all others when it comes to employability and that is:

  • ✅ The voices of their fellow students

So, one way to improve teaching and learning, is to maximise opportunities for students to learn from each other through peer learning and peer instruction. To do this, educators need to create more and better spaces for students to talk about their learning with each other and then amplify their voices.

There are lots of different ways to do this, but one of the most important is through Peer Assisted Study Sessions (PASS) at peersupport.manchester.ac.uk. These sessions allow more experienced students to pass on their knowledge to their less experienced, usually younger, peers. For example, the PASS scheme in Computer Science shown in figure 2, is run by my colleague Thomas Carroll. There is a focus on passing exams, but PASS is about much more than just improving students grades. It’s about students learning from and teaching each other as part of a student-led community.

Figure 2: Peer Assisted Study Sessions (PASS) allow more experienced students pass on their knowledge to their less experienced peers. First years have PASS1 (in yellow), run by second and third year students. Second years have PASS2 (in green), where students returning from internships and placements share their knowledge about job hunting and interviews. PASS3+ (in pink) is where our alumni can get involved. CC-BY-SA picture by yours truly

As well as helping students to pass academic exams, our PASS scheme also helps students to pass employers “exams”. This includes written exams such as job applications and oral exams such as interviews. This is a significant part of PASS2, where students returning from placements and internships share what they have learned with first and second year students.

Students are encouraged to take part in PASS, either as leaders, facilitators or participants, but the kinds of conversations that take place during these sessions often need to be amplified for those that aren’t in the room where it happens.

Over the last 12 months, I’ve been experimenting with using audio podcasts to record and publish some of these conversations as stories so they can heard by a wider audience. I’m calling them audio podcasts here to distinguish them from the video podcasts (lecture capture and catchup) you will find at mypodcasts.manchester.ac.uk. You can subscribe and listen to audio podcasts wherever you get your podcasts, details at the end of this post.

Essential podcast ingredients

Channelling my inner Lauren Laverne and Jim Al-Khalili, the podcast is a cross between the BBC shows Desert Island Discs and The Life Scientific. The resulting show is called Hearing your Future, shown in figure 3, because it is part of an undergraduate course and guidebook called Coding your Future aimed at all students of computing.

Figure 3: The Hearing your Future podcast is a cross between Desert Island Discs hosted by Lauren Laverne and The Life Scientific hosted by Jim Al-Khalili. Subscribe and listen wherever you get your podcasts. CC-BY-SA Portrait of Lauren Laverne by Jwslubbock on Wikimedia Commons w.wiki/6z4z, CC-BY-SA portrait of Jim Al-Khalili by Debbie Rowe at the Royal Society on Wikimedia Commons w.wiki/_w2fh, CC-BY-ND Hearing your Future artwork by Visual Thinkery.

The essential ingredients of this podcast are:

  1. Students: both graduands ready to graduate and recent graduates at the start of their career. Twelve students have been interviewed so far, with more episodes planned for the future.
  2. A decent microphone, see figure 4.
  3. Audio editing software, I’m using a free application called GarageBand apple.com/mac/garageband
  4. An audio podcast host, I’m using one called liberated syndication at libsyn.com
  5. Some open ended questions for students to answer
Figure 4: Any investment you make in recording technology will pay you back with higher-fidelity audio. This particular microphone, a Zoom H5, is handy because it can be used in a portable battery-powered mode or connected to a computer via USB. CC-BY-SA picture by yours truly.

The open-ended questions are key because I need to let students do most of the talking, acting as much more of a listener than a speaker. Think less Professor Monologue, the egocentric “sage-on-the-stage” who loves the sound of their own voice and more Professor Dialogue, the “guide-on-the-side” who facilitates discussion. [1] It sometimes takes effort for academics to suppress their public speaking instincts by talking less and listening more to what students have to say. Students are given five questions before the interview, with questions designed to encourage difficult conversations being optional. The five basic questions are:

  1. 🎸 What’s your story, (coding glory)?
  2. ✊🏽 Minority report (optional)
  3. 👑 You are the next vice chancellor (optional)
  4. 🍿 One tune, one book, one podast, one film
  5. ⏱ Time traveller, advice to your former self

Question one asks students to tell their story from why they studied computer science in the first place to where they are now. What obstacles have they faced in finding work and how did they overcome them? What has been their journey from student in year one to professional in year three or four? Every student has a different story to tell.

Question two asks students to reflect on their experience if they identify as a member of a minority group. What can employers and universities do to make campuses and workplaces more welcoming to members of their minority group? What has been their experience of being female, black, disabled or otherwise marginalised in computing? What can we do to make campuses more equal, diverse and inclusive spaces?

Question three asks students to imagine they are the next vice chancellor of the University of Manchester. Now that they are responsible for over 10,000 staff, 40,000 students and half a million alumni, what would they do to improve teaching and learning?

Question four is a personal one: students recommend a tune, a book, a podcast and a film and outline why these are important to them. Why do they recommend other students should watch, listen to or read them? This is the Desert Island Discs part, except we don’t cast students away to a remote island afterwards. It adds a personal touch to the stories students tell.

Finally, question five is another hypothetical one: given a time machine, if they could travel back to meet themselves in first year, what advice would they offer their former selves and fellow students about getting the most out of all the time and money they’ve invested in their University education?

I ask these simple, open-ended questions, sit back and enjoy listening to students answer them.

Everything I had to know, I heard it on my radio

As with radio broadcasting, there are costs and benefits of podcasting. The main cost is the time it takes to record, transcribe and edit each episode. Each interview takes an hour to record, more than an hour to transcribe and less than an hour to edit. These costs are relatively small, when you compare them to the cost of preparing a lecture (video lecture or live lecture), delivering a seminar, running a lab or facilitating a tutorial.

There are many benefits that this investment in podcasting buys. From a teaching point of view, I’ve learnt more about the harsh realities of job hunting faced by Generation Z. It also gives me seriously useful content in the form of case studies. So when I’m talking to students about the need for resilience in their job search I can tell Brian’s story, about finding a placement very late in the year (August) on LinkedIn. Don’t give up, it worked for Brian, maybe it will work for you too.

When discussing the importance of starting early, in first year, I can tell Alice’s story about how spring insights in her first year gave her some valuable experience to help her subsequent job applications stand out in second year and beyond. Start early, it worked for Alice, maybe it will work for you.

When discussing the inevitable rejection that comes with job applications, I can tell Amish’s story about being rejected by all five big tech companies (Microsoft, Google, Apple, Facebook and Amazon) before landing a role he enjoyed with Bloomberg. Learn to live with rejection, it’s a normal part of job hunting but it will most likely work out for you in the end.

When talking about not overlooking smaller employers, I can tell Raluca’s story about how she worked for a local company called Koder.ly in Oldham at the end of her first year, then moved onto CERN for her placement year and subsequent graduate role. You can start small, think big and remember that experience matters.

When discussing the importance of networking, I can tell Jonathan’s story about how he grew his professional network and found hidden vacancies by attending local tech meetups in Manchester. It’s not just what you know, it’s who you know.

These are just five short stories, from the twelve longer stories that students have shared with me. Recording them as podcasts has enabled me to amplify the student voice for more people to hear.

Another benefit of the podcast is, it has strengthened our community of students, alumni and employers. With permission, students have shared their LinkedIn profiles to facilitate digital networking. This means that students can find out about and connect with peers they might never otherwise have spoken to. It has also helped staff and employers understand better what challenges students face in an increasingly competitive job market.

So, what started as an experimental side project, has now become a key part of my teaching toolkit. It’s also has been rewarding to listen to and record students stories in an audio podcast format.

Conclusions: a good face for radio?

Podcasting is a low cost tool with many benefits for teachers and learners alike. Audio is fantastic medium for recording conversations and stories, especially if (like me), you have a “good face for radio”. [2] Most students are much more comfortable talking to a microphone than a video camera, because having a natter over a brew is a very natural format. Podcasting forces me to spend more time thinking about dialogue and less time making flashy animations and graphically-driven PowerPoint monologues. In this case, it’s enabled me to focus on what students are teaching other, rather than what I think they need to learn, so I can improve the Intended Learning Outcomes (ILOs) for my courses.

The student voices I’ve chosen to amplify have been deliberately “cherry picked” so I can’t pretend that their voices are representative of the entire study body. However, recording a few key voices documents how students learn professional skills for the workplace in a way that other students can learn from. A lot of higher education focuses on a narrow set of academic and technical skills, alongside fundamental knowledge. These are important, but a rounded education should develop a much broader set of softer personal and social skills that are just as important to talk about and recognise as the hard technical skills. Education is the sum of all these skills and knowledge, students play as important a role in teaching each other as their teachers do, shown in figure 5.

In the future, I plan to keep recording and broadcasting student voices to broaden the set of interviewees to include alumni who graduated further back in time. I welcome any comments on how these interviews can be improved in the future. Subscribe and listen wherever you get your podcasts:

As Stephen Fry points out, students play a crucial and often overlooked role in the education of their peers. Their voices need to be heard by a wider audience, not just their fellow students but their employers and educators too. Audio podcasting is a good way to amplify their voices. If you are a former student of Computer Science at the University of Manchester and would like to amplify your story about your personal journey from student to professional (and beyond), get in touch.

Figure 5: What is education the sum of? What students teach each other! Fry describes his student-centred view of education in The Fry Chronicles. [3] Public domain portrait of Stephen Fry by the US Embassy in London w.wiki/4wrn adapted using the Wikipedia App

References

  1. King, Alison (1993) From Sage on the Stage to Guide on the Side, College Teaching, Vol. 41, No. 1 , pp. 30-35, DOI: 10.1080/87567555.1993.9926781
  2. Mair, Eddie (2017) A Good Face for Radio: Confessions of a Radio Head Little Brown publishing , ISBN:9781408710678
  3. Fry, Stephen (2010) The Fry Chronicles Penguin books, ISBN:0718157915
A video of the presentation given at the #ITLConf23 conference in Manchester at the Pendulum Hotel, 6th July 2023, see doi.org/kk47 (Please excuse the audio errors and background noise in this recording, artefacts created by the software and microphone which I’m still learning to configure properly)

Acknowledgements

Thanks to all the students shown in figure 1 who took the time to tell me their stories: Raluca Cruceru, Jason Ozuzu, Brian Yim Tam, Carmen Faura Práxedes, Sneha Kandane, Alice Păcuraru, Jonathan Cowling, Ivo Iliev, Ingy Abdelhalim, Nadine Abdelhalim, Amish Shah & Pedro Sousa.

Thanks also to all the employers who’ve hosted these students as interns, placement students and graduates where they’ve learned professional skills that would be impossible to develop in a purely academic environment. These include Amazon Web Services aws.com, arm.com, home.barclays, home.cern, disney.com, disneyplus.com, equalexperts.com, Google, imago.cs.manchester.ac.uk (our student software company led by Suzanne Embury), infinityworks.com (part of Accenture), koder.ly, matillion.com, moneysupermarket.com, morganstanley.com, nomura.com, palantir.com, publicissapient.com, recursiveai.co.jp, thg.com and wise.com.

Thanks Jez Lloyd for getting me into podcasting with the CS@Manchester podcast.

Thanks to Thomas Carroll and Andrea Schalk who are responsible for current and previous incarnations of our PASS scheme in Computer Science. studentnet.cs.manchester.ac.uk/ugt/pass

Thanks Judy Williams, Jennie Blake, Hannah Cobb, Holly Dewsnip-Lloyd, Lisa McDonagh, Freya Corrywright, Beth Rotherham, Emma Sanders, Patricia Clift Martin and everyone at the Institute for Teaching and Learning (ITL) for organising the conference where this talk was first presented.

I look forward to an even bigger and better ITL conference in 2024!

July 17, 2019

Educating Computer Scientists: What should we discuss at #SIGCSE journal club?

fightclub

The first rule of journal club is, you do not talk about journal club. The second rule of journal club is, YOU DO NOT TALK ABOUT JOURNAL CLUB.* Discussions will go on as long as they have to. If this is your first time at journal club, you have to debate. Dress code: silly frocks and ridiculous hats are optional. Picture of my colleagues in the School of Computer Science ready for a graduation ceremony 2013, by Toby Howard.

So we’re starting a new Journal Club and Special Interest Group (SIG) for lecturers, teachers and course leaders in Manchester to discuss Computer Science Education (CSE). We’ll pick interesting papers, read them and then meet regularly to discuss them. It’s a bit like Fight Club but instead of beating each other up, we’ll “beat up” (review & critique) papers. Hopefully we’ll all learn something along the way. The first question to answer is, which papers should we discuss?

Computer Science (CS) is a young and professionally immature subject, it has only been taught at undergraduate level since 1965 in the UK. Across the pond in America, the Association for Computing Machinery (ACM) Special Interest Group on Computer Science Education (sigcse.org) only started as recently as 1968, making it a very spritely fifty years young. On educational timescales, computer science is a whipper snapper! Fifty years is peanuts when you compare it to the millennia that mathematics has been taught for. In ancient Greece the earliest lessons were mathematics hence μάθημα (mathematics) means the lesson and derivatives like μαθαίνω (matheno) mean to learn or to know. While the greeks built some impressive analogue computers, digital computers and computer science as we now know it, did not exist in Ancient Greece. 🇬🇷 

What this means is that there is plenty of evidence about what works (and what doesn’t) when teaching mathematics. In contrast, how to teach Computer Science, what should be taught and why, to whom and when are all open questions

So, to get the ball rolling here are nine papers that tackle some of these open questions in Computer Science Education. We’ll vote on the three most interesting papers and read them before meeting to review them. Many of these papers are likely to be of interest to “educators” in its broadest sense. That means anyone teaching coding, computer science, tinkering, hacking and software/hardware engineering at any level. Which includes primary schools, code clubs, bootcamps, CoderDojos, hackathons, secondary schools, CPD programmes, K-12 education, lifelong learning, staff training courses, onboarding, induction, adult education programmes, return to work schemes and so on. If you’d like to join us we’ll be meeting in the Kilburn building, Manchester, M13 9PL (mosty likely first week of September, date and time tbc, drop me a line). Otherwise enjoy reading the insights below (DOI’s link to originals which may be behind a paywall, freely accessible versions are provided where available). Some papers are quite short, and have been selected for the topic they discuss rather than the quality of the content.

Twenty dirty tricks to train software engineers by Ray Dawson

A classic paper from Ray Dawson in the department of Computer Science at Loughborough University describing dirty tricks they use to introducing the frustrating realities of a software engineering development to students.

“Many employers find that graduates and sandwich students come to them poorly prepared for the every day problems encountered at the workplace. Although many university students undertake team projects at their institutions, an education environment has limitations that prevent the participants experiencing the full range of problems encountered in the real world. To overcome this, action was taken on courses at the Plessey Telecommunications company and Loughborough University to disrupt the students’ software development progress. These actions appear mean and vindictive, and are labeled ‘dirty tricks’ in this paper, but their value has been appreciated by both the students and their employers. The experiences and learning provided by twenty ‘dirty tricks’ are described and their contribution towards teaching essential workplace skills is identified. The feedback from both students and employers has been mostly informal but the universally favourable comments received give strong indications that the courses achieved their aim of preparing the students for the workplace. The paper identifies some limitations on the number and types of ‘dirty tricks’ that can be employed at a university and concludes that companies would benefit if such dirty tricks were employed in company graduate induction programmes as well as in university courses.”

Identifying student misconceptions of programming by Lisa Kaczmarczyk et al

This paper by Lisa Kaczmarczyk et al (formerly University of California, San Diego) recently came top of the ACM SIGCSE Top Ten Symposium Papers of All Time. In Lisa’s own words from the reinventing nerds podcast “The paper is sharing the results of a research study about misconceptions that novice computer science students have. Computer science is also a very abstract topic and the mistakes that students make are often baffling. The paper reports on the misconceptions that students have and why they have them. It’s important because this paper was the first to apply rigorous research methods to investigating misconceptions.” From the abstract:

“Computing educators are often baffled by the misconceptions that their CS1 students hold. We need to understand these misconceptions more clearly in order to help students form correct conceptions. This paper describes one stage in the development of a concept inventory for Computing Fundamentals: investigation of student misconceptions in a series of core CS1 topics previously identified as both important and difficult. Formal interviews with students revealed four distinct themes, each containing many interesting misconceptions. Three of those misconceptions are detailed in this paper: two misconceptions about memory models, and data assignment when primitives are declared. Individual misconceptions are related, but vary widely, thus providing excellent material to use in the development of the CI. In addition, CS1 instructors are provided immediate usable material for helping their students understand some difficult introductory concepts.”

Stride in BlueJ – Computing for All in an Educational IDE by Michael Kölling et al

This paper by Michael Kölling et al describes an Integrated Development Environment (IDE) that combines the best features of visual programming languages (blockly, scratch etc) with text-based programming (such as Python, Java, C etc) for use in BlueJ.org.

“In introductory programming teaching, block-based editors have become very popular because they offer a number of strong advantages for beginning programmers: They avoid many syntax errors, can display all available instructions for visual selection and encourage experimentation with little requirement for recall. Among proficient programmers, however, text-based systems are strongly
preferred due to several usability and productivity advantages for expert users. In this paper, we provide a comprehensive introduction to a novel editing paradigm, frame-based editing – including design, implementation, experimentation and analysis. We describe how the design of this paradigm combines many advantages of block-based and text-based systems, then we present and discuss an implementation of such a system for a new Java-like language called Stride, including the results of several evaluation studies. The resulting editing system has clear advantages for both novices and expert programmers: It improves program representation and error avoidance for beginners and can speed up program manipulation for experts. Stride can also serve as an ideal stepping stone from
block-based to text-based languages in an educational context.”

  • Kölling, Michael; Brown, Neil C. C.; Hamza, Hamza; McCall, Davin (2019). “Stride in BlueJ — Computing for All in an Educational IDE”: Proceeding SIGCSE ’19 Proceedings of the 50th ACM Technical Symposium on Computer Science Education 63–69. DOI:10.1145/3287324.3287462

Ten quick tips for teaching programming by Neil Brown and Greg Wilson

This short paper from Neil Brown at King’s College London and Greg Wilson of software carpentry fame, is part of the popular Public Library of Science (PLOS) Ten Simple Rules series. The tips capture some ongoing research in listicle format.

“Research from educational psychology suggests that teaching and learning are subject-specific activities: learning programming has a different set of challenges and techniques than learning physics or learning to read and write. Computing is a younger discipline than mathematics, physics, or biology, and while there have been correspondingly fewer studies of how best to teach it, there is a growing body of evidence about what works and what doesn’t. This paper presents 10 quick tips that should be the foundation of any teaching of programming, whether formal or informal.

These tips will be useful to anyone teaching programming at any level and to any audience.”

How to Involve Students in FOSS Projects by Heidi Ellis et al

Initiatives like Google Summer of Code (GSoC) and Git going in FOSS aim to get students involved in Free and Open Source Software (FOSS) projects, through paid work and online tutorials. Some courses use FOSS projects to teach software engineering, though these are fairly unusual. How can we get more students (and teachers) involved in FOSS projects? This paper by Heidi J. C. Ellis provides some guidance

“Software projects are frequently used to provide software engineering students with an understanding of the complexities of real-world software development. Free and Open Source Software (FOSS) projects provide a unique opportunity for student learning as projects are open and accessible and students are able to interact with an established professional community. However, many faculty members have little or no experience participating in an open source software project. In addition, faculty members may be reluctant to approach student learning within such a project due to concerns over time requirements, learning curve, the unpredictability of working with a “live” community, and more. This paper provides guidance to instructors desiring to involve students in open source projects.”

  • Ellis, Heidi J. C.; Hislop, Gregory W.; Chua, Mel; Dziallas, Sebastian (2011). “How to involve students in FOSS projects” Frontiers in Education Conference (FIE) DOI:10.1109/FIE.2011.6142994 (ironically, if there is an open access version of this paper, I can’t find it! Another nominee for the Open Access Irony Awards)

A methodology for using GitLab for software engineering learning analytics by Julio César Cortés Ríos et al

This paper by Julio César Cortés Ríos at the University of Manchester describes using GitLab to analyse and improve courses.

“To bridge the digital skills gap, we need to train more people in Software Engineering techniques. This paper reports on a project exploring the way students solve tasks using collaborative development platforms and version control systems, such as GitLab, to find patterns and evaluation metrics that can be used to improve the course content and reflect on the most common issues the students are facing. In this paper, we explore Learning Analytics approaches that can be used with GitLab and similar tools, and discuss the challenges raised when applying those approaches in Software Engineering Education, with the objective of building a pipeline that supports the full Learning Analytics cycle, from data extraction to data analysis. We focus in particular on the data anonymisation step of the proposed pipeline to explore the available alternatives to satisfy the data protection requirements when handling personal information in academic environments for research purposes.”

Scaling Introductory Courses Using Undergraduate Teaching Assistants

Teaching computer science to large classes requires typically requires armies of teaching assistants, demonstrators. Your TA’s need to know their stuff and should be able to deal with students in a fair and consistent way. This paper is a medley of opinions from Jeffrey Forbes at Duke University, David Malan from Harvard University, Heather Pon-Barry from Mt. Holyoke College, Stuart Reges from the University of Washington and Mehran Sahami from Stanford University.

“Undergraduates are widely used in support of Computer Science (CS) departments’ teaching missions as teaching assistants, peer mentors, section leaders, course assistants, and tutors. Those undergraduates engaged in teaching have the opportunity to deeply engage with CS concepts and develop key communication and social competencies. As enrollments surge, undergraduate teaching assistants (UTAs) play a larger role in student experience and outcomes. While faculty and graduate student instructional support does not necessarily increase with the number of students in our courses, the number of qualified undergraduate teaching assistants for introductory CS courses should scale with the number of students in our courses. With large courses, the significance of the UTAs’ role in students’ learning likely also increases. Students have relatively little interaction with the instructor, and faculty may have more challenges monitoring and supporting individual UTAs. UTAs have a major role in affecting climate in computer science courses. The climate in large courses has substantial implications for students from groups traditionally underrepresented in computing. This panel will discuss how undergraduate teaching assistants can serve as a scalable effective teaching resource that benefits both the students in the course and the UTAs themselves.”

What Are We Doing When We Teach Computing & Programming by Sally Fincher

Two related papers by Sally Fincher at the University of Kent, the first published in 1999…

“The academic discipline of computer science uniquely prepares students for future study by teaching the fundamental construct of its practice-programming- before anything else. The disciplinary argument seems to run that if a student is not versed in the practicalities, then they cannot appreciate the underlying concepts of the discipline. This may be true. However an analogous simulation would be if it were thought necessary for architecture students to be taught bricklaying before they could appreciate the fundamentals of building design. This argument is clearly flawed when compared to endeavours such as the study of English Literature, which makes no claim to teach the practice of producing work before the study of the products of others work. It is possible that this is an argument of disciplinary maturity-that all disciplines have passed through a similar phase. This paper examines the emergent approaches being defined, all of which address the central concern of the teaching of programming and its relationship to the learning of computer science. It examines: the “syntax-free” approach of Richard Bornat and Russel Shackelford, the “problem-solving” approach of David Barnes (et al.), the “literacy” approach of Peter Juliff and Owen Astrachan and the “computation-as-interaction” approach of Lynn Andrea Stein. These approaches are discussed both in their own terms, and also placed in a preliminary taxonomic framework for the teaching of programming.”

….and the second published in 2015 (see comments on Mark Guzdial’s summary):

“Research on the cognitive, educational, and policy dimensions of teaching computing is critical to achieving “computer literacy.”

Making CS Learning Visible: Case Studies on How Visibility of Student Work Supports a Community of Learners in CS Classrooms by Amber Solomon et al

This is a paper by Amber Solomon et al from the Innovation and Technology in Computer Science Education (ITiCSE) conference is about reducing defensive and competitive (macho?) cultures in Computer Science  (via Mark Guzdials blog).

Modern learning theories emphasize the critical social aspect of learning. Computer science (CS) classrooms often have “defensive climates” that inhibit social learning and prevent the development of a community of learners. We believe that we can improve the social context of computer science learning by expanding CS learning beyond the single student in front of a display screen. Our theory is that the single student and single display inhibits collaboration and collaborative awareness of student work. In this paper, we present two case studies where we explored ways to make student work visible to peers. The first case study involved using a studio model for learning enabled by projection-based Augmented Reality (AR), and the second case study involves using a maker-oriented curriculum to make student work visible. Findings suggest the visibility of student work in CS classrooms helped support a community of learners: students collaborated, used each other as sources of inspiration, and felt more comfortable asking for help.

References and notes

*”You do not talk about Journal Club” is an adapted quote from the 1999 film Fight Club, see below. I’m only joking, you are of course welcome to talk to anyone who will listen about Journal Club.

Talking of David Malan, you can see his talk on making CS50 scale when he visited Manchester in 2017

Blog at WordPress.com.