I got my library card recently which is bringing me a lot of happiness, because now I can get books that otherwise I would not buy and find hidden gems like this one. This books is like the guide that this camera should had brought. It goes step by step trough all the details of what the camera can do an explains all the menus, if it wasn’t enough it also goes trought the trouble of providing the context that is needed in order to understand a photographic concept. My favorite chapter was the one about lenses because it explained all the types of lenses but gave concrete examples of the ones availables for this camera. I give this book a seven because is a starter book and i find it really useful to know your equipment at first but it looks like it won’t have much reuse value afterwards.
I read the book by Uncle Bob and went trough some of the exercises. I have to say he really knows what he wants to see when he opens a person code and he really places a lot of the lessons learned into it.
If you look trough the Content Table of the book you get a clear idea of what he promotes. I agree with a lot of the things he says and the TDD style of development he promotes. Getting things done first then done right to me it’s the only way of actually getting with functional and decent code. But i think that some of the proposed solutions like domain specific languages that are covered for testing purposes are to involved except for a few cases. This book is a good read like i mentioned and i would classify it as an optional read if you are interested in improving your coding style. In october will review Code complete has part of the review list which is the next one on my schedule. Currently i’m reading An introduction to Genetic Algorithms so my next posts might be related to that. Also in photography i’m going to make a video of how to clean your sensor. In terms of jewelcrafting i’m pretty much dead at the moment since my apt really does not help.
I just read this book and i think is one of the best books that i have read in terms of software process and explaining things clearly. The authors wen out of their wya to explain the methodologies they placed in practice and give concrete examples.
The table of content of the book looks like follows and i’m going to comment on it my thought of the chapter:
- A Pragmatic Philosophy – This chapter introduces the whole book and explain what being pragmatic is all about that is a philosphy of getting things done that are realistic in the best way possible and not trying to be perfecting understanding that we will make mistakes and the way to handle our approach.
- A Pragmatic Approach – On this chapters i read things that i loved like the tips on the evils of duplication but somethings that they would be impossible to apply in my day to day scenarios due to my type of work like the tracer bullets chapter and the use of specific domain languages. The ideas are still interesting and very much worth reading.
- The Basic Tools – The tools described in this chapter are the basic essentials for developing code. The part of source control and code generators seems like incredible good pieces of advise.
- Pragmatic Paranoia – This was the first chapter that i did not agree completely with what was said on the book completely the section of Design By contracts i don’t see how i could do that in my current workplace and the methodology followed not saying i sa bad idea just a bit impossible in my current situation. I would say the same thing with the Assertive Programming. This chapter has very good tips on how to go trought the life cycle of a project.
- Bend or Break – This is one of the best chapters in the book and i’m not going to spoil it worth reading every single page.
- While You Are Coding – This chapter explains practices to follow while programming and things to take into hand lessons learned from it are to refactor anything that needs it the moment you notice the need. Also good explanation of why is a problem to program by coincidence therefore simply by stumbling until you get to your end.
- Before the Project – Tackles requirements and when to actually start programming in the pragmatic way talks about iterating in order to get clearness.
- Pragmatic Projects -Explains that being pragmatic needs to be a team effort and not a one person effort.
Like i said at the beginning is an excellent book and i think that every programmer should have the oportunity of going trough it.
Now to read clean code by uncle bob.