From Principles to Practice with Class in the First Year
Authors:
- Sam Tobin-HochstadtSTSam Tobin-Hochstadt
- David Van HornDHDavid Van Horn
Preprint
Abstract
We propose a bridge between functional and object-oriented programming in the first-year curriculum. Traditionally, curricula that begin with functional programming transition to a professional, usually object-oriented, language in the second course. This transition poses obstacles for students, and often results in confusing the details of development environments, syntax, and libraries with the fundamentals of OO programming that the course should focus on. Instead, we propose to begin the second course with a sequence of custom teaching languages which minimize the transition from the first course, and allow students to focus on core ideas. After working through the sequence of pedagogical languages, we then transition to Java, at which point students have a strong command of the basic principles. We have 3 years of experience with this course, with notable success.Keywords
All Related Versions
This publication has 13 references indexed in Scilit:
- A functional I/O system or, fun for freshman kidsACM SIGPLAN Notices, 2009
- The chilling descent2008
- Design of class hierarchies2006
- Taming Java for the classroomACM SIGCSE Bulletin, 2005
- The structure and interpretation of the computer science curriculumJournal of Functional Programming, 2004
- The risks and benefits of teaching purely functional programming in first yearJournal of Functional Programming, 2004
- The BlueJ System and its PedagogyComputer Science Education, 2003
- DrScheme: a programming environment for SchemeJournal of Functional Programming, 2002
- A library to support a graphics-based object-first approach to CS 1ACM SIGCSE Bulletin, 2001
- Structure and Interpretation of Computer ProgramsComputer Music Journal, 1985