The Psychology of Computer Programming

The Psychology of Computer Programming This landmark classic is reprinted with new commentary and a Preface from the author Long regarded as one of the first books to pioneer a people oriented approach to computing The Psychology of

  • Title: The Psychology of Computer Programming
  • Author: Gerald M. Weinberg
  • ISBN: 9780442783105
  • Page: 266
  • Format: None
  • This landmark 1971 classic is reprinted with new commentary and a Preface from the author 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 Returning to topics that arThis landmark 1971 classic is reprinted with new commentary and a Preface from the author 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 Returning to topics that are strikingly relevant to today s issues in programming, Gerald M Weinberg provides a characteristically fresh perspective on his original insights, highlighting 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 enduring, straight from the heart observations on the human side of software engineering.Dorset House Publishing is proud to make this important text available to new generations of Weinberg fans and to encourage readers of the first edition to return to its valuable lessons.

    One thought on “The Psychology of Computer Programming”

    1. I picked up this book on a whim, purely based on the title. I didn't look at the copyright info or the introduction first, where I would have learned that Gerald Weinberg first wrote about programmer psychology in 1971.To my surprise, much of it aged well. Weinberg took an interesting approach when releasing a 25th anniversary "silver edition." Instead of editing out all of his references to COBOL, Fortran, and PL/I, or replacing them with anecdotes about C++ and Java, he left everything intact. [...]

    2. An insightful collection of essays that still resonate today even though some of its anecdotes reference punch cards. Egoless programming remains its strongest practice and one that is still not the norm. It's also staggering in its prescience. Although sometimes under different names, he predicts unit testing, code analysis tools, and countless other great ideas. I highly recommended it.

    3. This isn't a book about "computer programming", but about computer programmers. It holds up remarkably well more than 40 years after its publication date because even though the technology changes rapidly, the people creating it do not. Of course, not everything in the book has aged well. The discussion of "other programming tools" in the final chapter is fairly specific to an era of punch cards and shared terminals and should mostly be skipped. Also, there are some fairly dated views on the rol [...]

    4. TL;DR: don't waste your time, browse this blog instead.I was lured to this book by the title and ratings, and the latter still puzzle me.First of all, I cannot praise this book based on its contents because if there were any insights at the time of the first edition, they are at best commonplace today. How people engage in programming has changed a lot—environment, tools, languages, standard practices, they all have changed. Psychology has changed a lot (and the guy still swears by MBTI, that [...]

    5. Weinberg was one of the earliest authors who realized that computer programming is a human activity, and has a lot in common with other human activities. A programmer is reluctant to see the flaws in his code, so it must be checked by others. A programming language should be orthogonal because it is hard for a programmer to keep in his head, which features are enabled in which context. A programming project could never move forward if all interactions between the programmers follow the up-and-do [...]

    6. I was very disappointed. The title seemed so promising, but the book was just full of anecdotes and half-baked ideas. To his credit, Weinberg says early on that he only wrote the book to get people thinking about the psychology of computer programming. And he really did get me thinking about it and gave some interesting insights, but I was really hoping he would have thought things out more than he had.

    7. The occasional interesting tidbit, but mostly truisms and observations on processes that have changed a lot over the decades.

    8. Sometimes a bit hard to read as it is more of a scientific report yet written for a broad audience rather than easy-to-read kind-of-self-help bestseller. Some parts obviously obsolete in terms of technology (machines, languages, tools), others (not so surprisingly) still relevant - those revolving around human mind.

    9. This book is not interesting today if you're familiar with the topic. So no surprises for me. But need take into account the age! of the first edition! Interesting from historical point of view.

    10. The book has great early chapters. However, I do find the latter part of the book a bit more tedious as the author is trying to address a more social aspect of computer programming from a technical standpoint. I think it's hard to write about something social when the writer is approaching it as an engineering problem to solve.There are few major takeaways on computer programming:1. Think of computer programming as a social event. It is a group of people trying to build a product together. It is [...]

    11. there are a lot of interesting ideas in the book, but the contexts and examples are very outdated for me.

    12. Computer science evolves, but people's mind remains the same: it is an awesome book, full of still valid insights after 50 years.A must read.

    13. OK, it took me around 8 months to read this book. It was not a page turner. I brought it to Canada, and down into the Grand Canyon and back up. (It is also not a light book).It is considered a CS "classic", though, and my perseverance paid off, I think. The most interesting stuff was at the beginning, such as these tidbits I had notes on earlier:Although it is the "bane of scientific observation" the Hawthorne Effect (the process of being observed often motivates people to better performance) ca [...]

    14. It is not all that far away from the silver anniversary of the publication of this silver anniversary edition. Therefore, there is enough elapsed time for an effective look-back and what was a look-back.It is a fact that the effective shelf life of computing books is generally limited to the number of years that you can count on the fingers of one hand, excluding the thumb. This one is an exception, the content is timeless. It is true even though many of the processes and tactics for running a p [...]

    15. Although it was first published in 1971, most of this book still feels up-to-date, as long as you can ignore the occasional reference to punch cards and tapes. Despite all the change in software development, apparently some things don't change much. How we interact with each other, computers, and source code, remain stable.The text still seems relevant, and it contains some anecdotes that I recognise because they simply seem to have entered the general software development mythology. Apparently, [...]

    16. ❗ The book is must for everyone who participate in software development process.45 years old book, but it aged well. Human are still the same. It would be nice to see how Agile methodology was grounded on psychology, what it solves and what not.More important -there is no modern books on the same topic. The book is very dense. It touched lots of topics. For example, there is an opinion that programming was more female-friendly in 60-70s. Author shows stereotypes about females - he suggests til [...]

    17. This book should be required reading for programming managers everywhere alas, that's probably too much to hope for and programmers will have to settle for reading it themselves. Read it, think about the raised issues, answer the questions at the end of each chapter - you'll never look at the office the same way again.The text is over 45 years old and the code snippets in languages of the day such as PL/I or FORTRAN may be quite hard to appreciate today. Additionally, the book makes some questi [...]

    18. Like Mythical Man Month, this book was written in another era of computing. Nonetheless, many concepts, like egoless programming, and the effect of seemingly unrelated workplace changes to coding, like the location of the coffee machine, still apply today. Even the more aged comments are still informative of the history of computing for programmers like myself, who've grown in the world of fast personal computers and very advanced operating systems. I think I understand my co-workers better now [...]

    19. I read this back in college (20-some years ago), several times; it's an entertaining investigation of the people who create software - and how their psychology affects the resulting products. Even after 20 years I recall Weinberg talking about a case where petty jealousies in a programming team led to errors in program output years later (after an upgrade) - errors that were only uncovered after some reminiscing by the original team gave a clue to where the new error might be: not in the section [...]

    20. I first came across this book probably in the late 80's. Even then some of it seemed a little dated and I'm sure it must seem even more so now. However, despite all of that, I would still strongly recommend this book to anyone who ever gets involved with any form of software development or more generally any aspect of creativity in highly technical fields - particularly where teamwork is required.Egoless programming is just as pertinent now as it ever was to Gerry when he wrote this book.

    21. + a book with code snippets in PL/I and memory measured in KB is fun to read+ anecdotes supporting the author's ideas are also fun+ maybe there were some good points I'll find useful - we'll see- the language is a bit complicated: some sentences are just huge and hard to parse- there's too much introductions, motivations and random musings- some of the questions posed are obsolete, some have been answered definitively during the last 40 years

    22. This is an excellent book, the ideas it promotes are still relevant today (several decades after the it was published).It is quite interesting to observe how languages evolved, how some of them got things right And how some are throwing programmers into traps that were known many years ago.Overall, I really enjoyed this one!

    23. As a programmer that has spent most of his time working along, The Psychology of Computer Programming provided some interesting insights into team dynamics. I wish everyone that I will have to work with (and for) in the future will have read his book.

    24. amazing book! it's interesting to read about programmers and their problems 40 years ago and see that actually nothing's changed. great great great book. I have enjoyed reading it and surely learnt a lot during reading.

    25. A fantastic, practical introduction to thinking about the psychology of computer programming.Unlike most books, the author isn't afraid to say "we don't know" when there's a question they don't have the answer to. It's a refreshingly honest feeling book.

    26. I found this book very helpful, in that it gave me a fresh picture of how life could be inside a high-tech organization (Info Tech in my case). Very accessible, in contrast to all the tech manuals I had to read.

    27. Fascinating perspective, a view that is very often missing. Amazing how appropriate and applicable ideas from this book are today! Over 25 years later. I wish more people understood the context of programming form the psychological perspective.

    28. While this book was written in 1971, it's amazing how much of it still rings true today. It's a bit tedious at times, and some chapters can be skipped outright, but the good parts are worth a read.

    Leave a Reply

    Your email address will not be published. Required fields are marked *