Pete Goodliffe- Becoming a better Programmer, O’Reilly INC. An Illustrative approach to programming by Noreen Sarai

Pete Goodliffe- Becoming a better Programmer, O’Reilly INC.

An Illustrative approach to programming by Noreen Sarai

There could have been no better way of making already programmers or potential programmers be aware of the basic self requirements for coming up with a code than the way Pete Goodliffe described it in his book, Becoming a better Programmer. The book spans with a series of chapters which synchronous with each other, having each chapter adding value to the next chapter. It’s a book that’s explains the mandatory items that when possessed someone can improve his/her skills when it comes to the art of writing programs. The book starts by highlighting the necessary attitude required to become a programmer and concludes by explaining how one can deliver when it comes to programming.

Programming is technical concept, but the way it was presented in the book made the whole approach move outside of its realm. I liked very much the angle taken by the writer in expressing his points, through use of very good illustrations. It made the art of programming a more illustrative process. Usually many people don’t like programming because they believe its very hard, but by using clear day to day illustrations helps readers to be more eager to read and to learn the art of programming. Take for instance the aspect of relating programming to food as illustrated in chapter 14, to marriage on page 259 and to rules of travelling by airplanes as used in chapter 15. Readers are bound to understand more what the author is talking about as illustrations used are very well known to them.

At end of each chapter the author made use of very good self assessment questions which somehow force the reader to think and answer rather than just picking answers from what has been read.

The author used a statement “poor programmers need more rules "in chapter 15. Here I felt the more you overload them with rules of programming the more they do not understand. As most poor programmers do not even understand the few basic rules that exist in programming languages.

Throughout the whole book the author made use of vocabulary which might not be understood by some readers. After all the book is meant for all levels of people and believe me there are some naive aspirant programmers out there.

Otherwise the illustrative approach taken by author was good and readers are bound to like it.