Entry Decker:1994:TRW from sigcse1990.bib

Last update: Wed Sep 26 02:07:32 MDT 2018                Valid HTML 4.0!

Index sections

Top | Symbols | Numbers | Math | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

BibTeX entry

@Article{Decker:1994:TRW,
  author =       "Rick Decker and Stuart Hirshfield",
  title =        "The top 10 reasons why object-oriented programming
                 can't be taught in {CS 1}",
  journal =      j-SIGCSE,
  volume =       "26",
  number =       "1",
  pages =        "51--55",
  month =        mar,
  year =         "1994",
  CODEN =        "SIGSD3",
  DOI =          "https://doi.org/10.1145/191033.191054",
  ISSN =         "0097-8418 (print), 2331-3927 (electronic)",
  ISSN-L =       "0097-8418",
  bibdate =      "Sat Nov 17 18:57:24 MST 2012",
  bibsource =    "http://portal.acm.org/;
                 http://www.math.utah.edu/pub/tex/bib/sigcse1990.bib",
  abstract =     "Over the past year we have changed our CS 1 course
                 from a standard Pascal-based, procedural programming
                 course into one that emphasizes C++ and object-oriented
                 programming (OOP). While our experience to date
                 indicates that this was a good decision for both our
                 students and our department, the decision did not come
                 easy. We struggled long and hard with many, if not
                 most, of the questions and issues that have come to be
                 associated with teaching OOP to undergraduates. This
                 paper recounts our struggles, and presents our
                 responses to the more serious of the pedagogical
                 questions that we considered. In hindsight, many of the
                 reasons we came up with for not using OOP in CS1 are
                 seen to reflect our lack of understanding of the
                 paradigm, our fear of the language, and our past
                 experience teaching Pascal and the procedural paradigm.
                 Furthermore, we believe that our reservations (which
                 appear to be quite common) stemmed from a growing body
                 of misleading OOP folklore that is contrary to our
                 experience and that this paper attempts to dispel.",
  acknowledgement = ack-nhfb,
  fjournal =     "SIGCSE Bulletin (ACM Special Interest Group on
                 Computer Science Education)",
  journal-URL =  "http://portal.acm.org/browse_dl.cfm?idx=J688",
}

Related entries