Exploring the Impact of Exposing Command Line Programming to Early CS Majors (An HBCU Case Study)

Edward Dillon; Krystal L. Williams; Ashley Simone Pryor; Theodore Wimberly Jr.; Mariah McMichael; Abisola Mercy Arowolaju; Donald Bernard Davis; Toluwanimi Ayodele

Download Paper | Permalink

Conference: 2024 ASEE Annual Conference & Exposition
Location: Portland, Oregon
Publication Date: June 23, 2024
Start Date: June 23, 2024
End Date: July 12, 2024
Conference Session: Programming Education 2
Tagged Division: Computers in Education Division (COED)
Permanent URL: https://peer.asee.org/47434

Request a correction

Paper Authors

biography

Edward Dillon Morgan State University

visit author page

Dr. Dillon received his B.A. in Computer and Informational Science from the University of Mississippi in 2007. He would go on to obtain his Masters and Ph.D. in Computer Science from the University of Alabama in 2009 and 2012, respectively. Dr. Dillon is a newly tenured Associate Professor in the Department of Computer Science at Morgan State University. Prior to his arrival to Morgan State, Dr. Dillon served as a Computer Science Instructor at Jackson State University (2012-2013), and a Postdoctoral Researcher at Clemson University (2013-2014) and the University of Florida (2014-2016). His research focuses on human-centered computing, computer science education, social computing, and broadening participation in computing. Dr. Dillon has received >$750k in research funding and awards from external agencies and non-profit organizations, including the National Science Foundation (NSF), the Maryland Pre-Service Computer Science Teacher Education Program (MCCE), and the Collaborative Research Experience for Undergraduates (CREU - CRA-WP). Dr. Dillon currently serves as a Co-PI for the STARS Computing Corps, which recently has been renewed for funding by NSF. He has also conducted a Faculty in Residency at Google during the summer of 2018 to learn more about this company’s culture, practices, and to understand the expectations for candidates (e.g. aspiring CS majors) who pursue career opportunities at this company and related prominent companies in tech.

visit author page

author page

Krystal L. Williams University of Georgia

biography

Ashley Simone Pryor Morgan State University

visit author page

College junior and Vice President of the Society for the Advancement of Computer Science, a Morgan State University ACM chapter. Active member of Morgan State's Women in Computer Science organization.

visit author page

author page

Abstract

Learning to program is an essential part of developing computational skills amongst computer science (CS) majors. Yet, CS majors can encounter programming as a barrier and in many cases leave the field altogether. The learning process that CS majors encounter while developing their programming skills is multifaceted. They are expected to: 1) grasp necessary programming concepts, paradigms, and data structures, 2) become adept with employing the appropriate syntax and semantics for a given programming language used for code development, and 3) exhibit a proficiency for effectively operating a programming tool/editor assigned.

Effective approaches for teaching CS majors how to program has garnered much attention. When emphasizing the types of tools/editors that CS majors operate while programming in addition to these tools’ potential impact to aid the students’ development of their programming skills, much of this work seen in literature has focused on visual-based tools/editors that exhibit adequate affordance to the student for operation during code development (e.g. integrated development environment (IDEs)). In contrast, there are minimal studies that directly explore relative pedagogical impacts involving non-IDE based tools that are less visual in appearance and exhibit a lower operative affordance to the student (e.g. command-line based tools/editors). Moreover, there are even fewer studies that directly compare the impacts of IDEs and command line environments, respectively, on student learning.

This article discusses a case study that exposed early CS majors, enrolled in either CS2 or an Object-Oriented Programming course at a Mid-Atlantic Historically Black University in the United States, to command line programming. This study was conducted over a span of six semesters (Fall 2020 – Spring 2023). During these semesters, students in both courses, respectively, were assigned a command line workflow module to complete beginning in week 3. This module required these students to: 1) install a Unix-like command-line interface named Cygwin unto their personal computers, 2) learn a series of commands for navigating the file/directory system via the Cygwin interface, and 3) become proficient in building, compiling, and executing/interpreting programs while using the appropriate commands via the Cygwin interface. Students who owned a Mac-based computer were permitted to use the embedded Unix-based terminal interface on their Mac to complete this module.

To gauge the impact of command line usage on the students in these courses, two surveys were administered at different points of the semester to capture both performance and psycho-social related feedback about the students’ experiences. Overall, it was revealed that the CS2 students tended to exhibit an unfavorable disposition towards command line programming, which was also reflected in their initial struggle to adjust to using a command line tool. On the other hand, the OOP students showed a better performance and disposition towards command line programming, but this could have been influenced by acquired experiences both prior and external with using such tools.

Citation
Format

Dillon, E., & Williams, K. L., & Pryor, A. S., & Wimberly Jr., T., & McMichael, M., & Arowolaju, A. M., & Davis, D. B., & Ayodele, T. (2024, June), Exploring the Impact of Exposing Command Line Programming to Early CS Majors (An HBCU Case Study) Paper presented at 2024 ASEE Annual Conference & Exposition, Portland, Oregon. https://peer.asee.org/47434

TY - CPAPER
AB - Learning to program is an essential part of developing computational skills amongst computer science (CS) majors. Yet, CS majors can encounter programming as a barrier and in many cases leave the field altogether. The learning process that CS majors encounter while developing their programming skills is multifaceted. They are expected to: 1) grasp necessary programming concepts, paradigms, and data structures, 2) become adept with employing the appropriate syntax and semantics for a given programming language used for code development, and 3) exhibit a proficiency for effectively operating a programming tool/editor assigned.

Effective approaches for teaching CS majors how to program has garnered much attention. When emphasizing the types of tools/editors that CS majors operate while programming in addition to these tools’ potential impact to aid the students’ development of their programming skills, much of this work seen in literature has focused on visual-based tools/editors that exhibit adequate affordance to the student for operation during code development (e.g. integrated development environment (IDEs)). In contrast, there are minimal studies that directly explore relative pedagogical impacts involving non-IDE based tools that are less visual in appearance and exhibit a lower operative affordance to the student (e.g. command-line based tools/editors). Moreover, there are even fewer studies that directly compare the impacts of IDEs and command line environments, respectively, on student learning.

This article discusses a case study that exposed early CS majors, enrolled in either CS2 or an Object-Oriented Programming course at a Mid-Atlantic Historically Black University in the United States, to command line programming. This study was conducted over a span of six semesters (Fall 2020 – Spring 2023). During these semesters, students in both courses, respectively, were assigned a command line workflow module to complete beginning in week 3. This module required these students to: 1) install a Unix-like command-line interface named Cygwin unto their personal computers, 2) learn a series of commands for navigating the file/directory system via the Cygwin interface, and 3) become proficient in building, compiling, and executing/interpreting programs while using the appropriate commands via the Cygwin interface. Students who owned a Mac-based computer were permitted to use the embedded Unix-based terminal interface on their Mac to complete this module.

To gauge the impact of command line usage on the students in these courses, two surveys were administered at different points of the semester to capture both performance and psycho-social related feedback about the students’ experiences. Overall, it was revealed that the CS2 students tended to exhibit an unfavorable disposition towards command line programming, which was also reflected in their initial struggle to adjust to using a command line tool. On the other hand, the OOP students showed a better performance and disposition towards command line programming, but this could have been influenced by acquired experiences both prior and external with using such tools.

AU - Edward Dillon
AU - Krystal L. Williams
AU - Ashley Simone Pryor
AU - Theodore Wimberly Jr.
AU - Mariah McMichael
AU - Abisola Mercy Arowolaju
AU - Donald Bernard Davis
AU - Toluwanimi Ayodele
CY - Portland, Oregon
DA - 2024/06/23
PB - ASEE Conferences
TI - Exploring the Impact of Exposing Command Line Programming to Early CS Majors (An HBCU Case Study)
UR - https://peer.asee.org/47434
ER -