As a third blog post for course of ECIP, Reading and Oral Skills Spring 2020 it was assigned that we should write a little book report about book we have read. I chose book Pragmatic Programmer by David Thomas and Andrew Hunt.
Instead of reading, I started to listen this book as an audiobook through Amazon Audible. This book was one of the many options were suggested in the course instructions. I ended up picking this one because it looked like something that is going to offer some fundamentals needed to be understood if one is seeking for career of programmer. I expected to find some basic philosophies behind working with code, instead of deep technical details. I found both of them.
Book has been so far interesting and it’s full of helpful content for it-student. I think it’s good to read or listen this kind of books as early as possible, because later new routines and habits might be more difficult to implement for one’s programming workflow.
First chapter I read was about pragmatic philosophy and second one was about basic tools. First chapter named “Pragmatic philosophy” was about seeing a bigger picture behind of programming work. Pragmatic perspective includes at least these perspectives: practical attitude, decision making, style and philosophy for work, skill to make compromises, taking responsibility of one’s work, lifelong learning and communication.
Second chapter I read is about tools for programming work. Name of that chapter is “The basic tools”. In this chapter authors are suggesting some basics tools for programming and how trying new ones can improve you as a programmer. Also use of paper and pen were encouraged.
I found that book was full of good material to use and learn. I understood that some parts of book will be more relevant later when my practical knowledge about software project grows. Most beneficial part of the book gave me understanding and motivation learning to write code in new environments and to try new programming languages to became better in solving problems with any programming language.
I can recommend this book everyone who is on their path of software engineering. I believe it will be helpful for most of it-crowd, even people with more experience.
Thank you for reading!
Best regards, Iikka Järvenpää