Industry reaction to computer science education

Authors:
George Dodd;Fred A. Gluckson
Affiliations:
Computer Technology Department, GM Research Labs, Warren, Michigan;EDP Systems Department, National Bank of Detroit, Detroit, Michigan
Venue:
SIGCSE '74 Proceedings of the fourth SIGCSE technical symposium on Computer science education
Year:
1974

Citing 0
Cited 7

A survey of the literature in computer science education since curriculum '68

Communications of the ACM
The mathematics component of the undergraduate curriculum in computer science (Panel Discussion)

SIGCSE '81 Proceedings of the twelfth SIGCSE technical symposium on Computer science education
Industrial software training opportunities for computer professionals

ACM '81 Proceedings of the ACM '81 conference
On the need for teaching problem-solving in a Computer Science Curriculum

SIGCSE '75 Proceedings of the fifth SIGCSE technical symposium on Computer science education
A Computer Science Practicum

SIGCSE '75 Proceedings of the fifth SIGCSE technical symposium on Computer science education
The Master's Practicum: A bridge over the Industry/University Gap

SIGCSE '75 Proceedings of the fifth SIGCSE technical symposium on Computer science education
Computer science education for majors of other disciplines

AFIPS '75 Proceedings of the May 19-22, 1975, national computer conference and exposition

Quantified Score

Hi-index	0.03

Visualization

Abstract

Today, undergraduate Computer Science Education teaches mechanics without teaching problem solving. Typical curricula include courses in assembler languages, compiler theory, list processing, and automata theory. Every MS degree holder, and most BS degree holders, know Polish notation and have written parts of compilers. However, few of them have ever learned to write a program that can be easily enhanced or respond to changes as new management (instructor) requirements are set forth. Even fewer can read a program and describe what it does or debug a system consisting of ten or more modules.