What do you think?
Rate this book
Journey of the Software Professional: The Sociology of Software Development
A comprehensive guide to the software development process that will help software developers at every stage of their improving personal performance, learning to work well in a team, and managing to create an environment where others can be most effective. Addresses the psychological and sociological aspects of software development, presenting a thorough model of individual and collective software problem-solving behavior, and practical techniques for enhancing the process. Covers the structures, processes and outcomes common to most software development projects, and how to improve them. Presents ideas on using tools and training more effectively, and on improving the performance of teams. Shows how to build on your personal and management successes, and avoid the most common errors. Programmers, developers, software managers, students, and anyone involved in the software creation process.
- GenresComputers
447 pages, Hardcover
First published October 17, 1996
2 people are currently reading
68 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
September 9, 2021
I give a five star review if I believe that I will re-read or repeatedly refer back to a book and I am likely to recommend it to colleagues as essential reading.
Please do not be put off by this book having been published in 1997, I found it to be surprisingly relevant even to today’s standards, often foreshadowing practices touted as “modern” (aside from section 16.2, on release strategy, where releases still necessitated “diskettes and manuals and shipping”).
The practicalities of working within a software organisation are written from the perspective of a developer. There are sections of advice geared towards developers and management side-by-side; it’s useful for each to see the perspective of the other.
The book is structured in five parts:
i. Individual theory (Mental processes of software development, cognitive models)
ii. Individual practice (Structure, Process, Outcome (SPO) & future perfect thinking)
iii. Team theory (Organizational models, collective behaviour)
iv. Team practice (Team effectiveness, standards, trust, system architectures, structure)
v. Context (Working environments)
There is such a bombardment of ideas, both in depth and breadth that I found it quite a long slog to read. I often found myself remembering relatable past events and had ideas sparking off all over the place. The notes I took will be invaluable for when I refer back to this in future, as I’m extremely sure I will.
Please do not be put off by this book having been published in 1997, I found it to be surprisingly relevant even to today’s standards, often foreshadowing practices touted as “modern” (aside from section 16.2, on release strategy, where releases still necessitated “diskettes and manuals and shipping”).
The practicalities of working within a software organisation are written from the perspective of a developer. There are sections of advice geared towards developers and management side-by-side; it’s useful for each to see the perspective of the other.
The book is structured in five parts:
i. Individual theory (Mental processes of software development, cognitive models)
ii. Individual practice (Structure, Process, Outcome (SPO) & future perfect thinking)
iii. Team theory (Organizational models, collective behaviour)
iv. Team practice (Team effectiveness, standards, trust, system architectures, structure)
v. Context (Working environments)
There is such a bombardment of ideas, both in depth and breadth that I found it quite a long slog to read. I often found myself remembering relatable past events and had ideas sparking off all over the place. The notes I took will be invaluable for when I refer back to this in future, as I’m extremely sure I will.
Displaying 1 of 1 review