[Book Review]: The pragmatic programmer from journeyman to master

The book “the pragmatic programmer from journey to master” is written by Andrew Hunt and David Thomas. The book contains 8 chapters with 321 pages chapter 1: a pragmatic philosophy chapter 2: a pragmatic approach chapter 3: the basic tools chapter 4: pragmatic paranoia chapter 5: bend, or break chapter 6: while you are coding chapter 7: Before the project chapter 8: pragmatic projects

What problems does this book solve?

  • Explains the myth that there is no such thing as the best solution
  • The qualities that needed to become a pragmatic programmer
  • How the famous broken window theory is related to software entropy
  • Explained how perfection is maintained by comparing with a real-life situation like Gardner and  the garden
  • The story stone and boiled frogs have a deep meaning related to start-up fatigue and how people find it easier to join an ongoing success
  • How software disasters start with small things to notice then turns into a disaster
  • The evils of duplication in software development and surviving in a world of scarcities with limited time and resources.
  • The concept of orthogonality in the software development process with overlap issues
  • How time pressure tempted us to copy but in reality there is no such thing as short cuts, always short cuts make for long delays
  • The concept of reversibility and the danger of thinking the only idea you have.
  • The concept of estimating to know whether this is practical and where do estimates come from
  •  A list of basic tools that are essential for software developers like git, debugging tool, notepad.
  • Designing modules by contract and documenting and verifying, preconditions, postconditions, and an exception
  • The concept of an event and event minimize coupling b/w objects
  • Blackboard approach to co-ordinate workflow.
  • Programming by coincidence and how to program deliberately.
  • The concept of refactoring and when should you refactor
  • The requirements pit, documenting requirements, template for gathering requirements
  • Ruthless testing, what to test

My view of the book

 The book is written to give tips to software developer’s and the book contains total 70 tips in it, I really like stories which he used to explain the software development concept, like broken window theory, stone soup, and boiled frogs

For me, it is important making notes whatever I read, so I made notes of this book if I forget something I can go through notes easily, by reading this book it feels like the author had a broad experience in software development.

Leave a Reply