The Psychology of Computer ProgrammingDiscover or Revisit One of the Most Popular Books in Computing This landmark 1971 classic is reprinted with a new preface, chapter-by-chapter commentary, and straight-from-the-heart observations on topics that affect the professional life of programmers. Long regarded as one of the first books to pioneer a people-oriented approach to computing, The Psychology of Computer Programming endures as a penetrating analysis of the intelligence, skill, teamwork, and problem-solving power of the computer programmer. Finding the chapters strikingly relevant to today's issues in programming, Gerald M. Weinberg adds new insights and highlights the similarities and differences between now and then. Using a conversational style that invites the reader to join him, Weinberg reunites with some of his most insightful writings on the human side of software engineering. Topics include egoless programming, intelligence, psychological measurement, personality factors, motivation, training, social problems on large projects, problem-solving ability, programming language design, team formation, the programming environment, and much more. Dorset House Publishing is proud to make this important text available to new generations of programmers--and to encourage readers of the first edition to return to its valuable lessons. |
Contents
PROGRAMMING | 2 |
What Makes a Good Program? | 15 |
How Can We Study Programming? | 27 |
Copyright | |
12 other sections not shown
Other editions - View all
Common terms and phrases
ability amateur asked assembly language batch better bombed the system COBOL cognitive dissonance compiler computer programming course debugging difficulty documentation Dorset House Publishing effect efficiency egoless programming environment errors example experience factors FORTRAN Gerald give goals going grammers gramming important individual intelligence job control job control language language design least less limitations look machine machine language MBTI measure mentation ming motivation never observation operating system organization performance perhaps personality PL/I possible probably problem solving produce professional programmer programmer's programming language programming project programming team project manager psychological Quality Software Management question reason Sackman schedule seems simply situation social specifications statement structure subroutine success syntax team leader team members terminal things tion trying turnaround typical understand write York