If last week’s book review was too complicated for you, perhaps this book is more suited for you. Less design patterns, but a funnier way to describe them.
As I’ve said before, I’ve done several book reviews in the past. I will start with a small serie on design patterns books.
This book is one of the “must-have” in your library. If you write some code or if you manage some IT or Computer Science projects, you will have this book to lay down the basic software architecture.
Like other programming models, there are some patterns in selecting the right parallel solution when it comes to designing a parallel application. This is what this book is about. The solutions may be obvious, but patterns aften are.
I came across the issue of how to teach a trainee how to write a parallel finite-difference time-domain (FDTD) method. There are a lot of books on the FDTD, but only a few on parallel ones. So I’ve decided to go for this book, knowing that some chapters won’t apply to our job (wave equations). My goal was to seek a book that would explain the basics of my issues.
I’m a very curious guy, and I wanted to know who is looking at my blog, and for my wife, who is interested by what is viewed on her decoration site (in construction as she wants to make a living of decoration advice). With my hosting service, I have access to Awstats, but Google Analytics seems better suited for data analysis. And this is what this book explains.
When I started my new job three months ago, I didn’t know how to write a Fortran program. I had to modify an already existign Fortran 77 program to enhance and parallelize it. So I went to the library and I took this book aimed at people like me.
This is the first time I will review a book on something I’m not familiar with at all. I’ve started now for more than two months a new job related to geophysics, and I had to catch up with my colleagues.
I’ve stopped studying geology ten years ago, so this is a review from someone who is learning geophysics and who wants to have a quick and global look on the different fields of geophysics.
Contrary to what the title may hint to, this book is an introduction to C++ and the Qt library. And in the process, the authors tried to teach some good practices through design patterns. So if you’re a good C++ or Qt programer, this book is not for you. If you’re a beginner, the answer is in my review.
I got this book from a partnership between http://www.developpez.com/ and O’Reilly. Thanks to both of them.
What defines “beautiful code”? How do people think a beautiful code should look like? This isn’t a simple question to answer, so this book asked several lead programmers (Ruby, Python, C, C++, Java, Perl, …) some beautiful code they wrote or they encountered. And if some want to answer “think about a robust, simple to extend code and that will be it” (and I would be one of them before I read the book), there are some code that would not fit this profile.