The second edition of Explorations in Quantum Computing is very disappointing because it could have been much better.
The main problem I found in this...moreThe second edition of Explorations in Quantum Computing is very disappointing because it could have been much better.
The main problem I found in this book is the staggering number of obvious, distracting typos, mistakes, and errors that are evident of a very poor editing process (or the lack thereof). I was regularly distracted by incomplete sentences, unclosed parenthetical sentences, and, more alarmingly, inconsistent mathematical notations in almost every chapter. Such mistakes strengthen the association I already have between Springer and poor editing.
It even gets worse: there are notes that someone (apparently, the author) has left for himself! The caption of figure 13.7 on page 532 is:
BB84 protocol TEST ONLY. This figure is copyright protected and cannot be used. A new figure conveying similar information needs to be drawn here. Illustration of the BB84 QKD protocol.
The caption of figure 13.17 on page 543 starts with "this figure needs to be redrawn showing similar concepts."
As for the scientific value of the content, I can't deny that some sections, especially the ones on computational complexity and computational phase transitions, were somewhat informative and interesting for a beginner in quantum computing like me. Nevertheless, the distracting typos and mistakes overshadowed this value and ruined my reading experience.
In a nutshell, the second edition of Explorations in Quantum Computing is an overpriced editorial mess that should have never gone to press. You definitely should not waste your money on this edition; you probably should not waste your time on it either.(less)
IMHO, this book is not bad enough to be totally ignored, but it is not good enough for me to spend my money on it.
This brief book provides an overview...moreIMHO, this book is not bad enough to be totally ignored, but it is not good enough for me to spend my money on it.
This brief book provides an overview of bioinformatics and the application of AI techniques to its problems. Personally, and as a computer scientist and an AI researcher with little background in biology, I found the chapters on the basics of molecular biology (Chapter 1), the challenges of bioinformatics (Chapter 2), genetic programming (Chapter 9), and cellular automata (Chapter 10) to be the most interesting/informative ones.
On the negative side, there are a considerable number of typos that are quite easy to spot it makes you question the editing process. Furthermore, the discussion of computational complexity classes (Section 3.9) contains some false statements. For example, it is claimed towards the end of the first paragraph on page 97 that "if a polynomial-time solution can be found for just one of the problems in the NP class, there will be polynomial-time solutions for all problems in the NP class." This could be another typo where the first "NP" should have been "NP-complete." Another example is the statement that "so far no one has managed to conclusively prove that a single problem in NP actually falls in the class P." This statement is false because the class P is contained in the class NP. In other words, there are many problems in NP that fall in P, namely all the problems of P.
Bottom line, if you are looking for a "starting point" for the application of AI techniques to bioinformatics, this book is not bad. Then again, Wikipedia is not a bad starting point either.(less)
The Elements of C# Style is a short, handy, and easy to understand style guide for the C# programming language.
This book follows the pattern used in m...moreThe Elements of C# Style is a short, handy, and easy to understand style guide for the C# programming language.
This book follows the pattern used in most style guides: a list of 174 rules, each containing a short explanation plus some examples of correct, and occasionally incorrect, use. The rules offer standards and guidelines that cover formatting, naming, documentation, programming, and packaging.
You are not expected to agree with all of the rules, but the specifics of a style doesn't really matter; what matters most is that you follow some "good" coding style consistently, and the advice offered by this book is pretty much in line with what is found in other "good" programming style guides.
In a nutshell, if you want to write C# code in a consistent style, this book is worth having nearby, especially if you write code as part of a team.(less)