97 Things Every Programmer Should Know (Anglais) Broché – 2 mars 2010
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant consulté cet article ont également regardé
Descriptions du produit
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur l'auteur
Dans ce livre(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
Tout est fait pour que ce livre devient une référence vers laquelle le développeur puisse revenir quand il cherche des conseils pour améliorer ses pratiques. La table des matière à double entrée (chronologique et par catégorie) facilite une lecture thématique sur les versions papier ou PDF, les articles courts se prêtent bien à une lecture sur un terminal mobile.
Cependant, si vous êtes déjà un développeur expérimenté, de nombreux conseils vont vous sembler basics tels que "Put Everything Under Version Control" ou "Don't Repeat Yourself".
Au final, même si tout développeur peut bénéficier de sa lecture, un investissement dans ce livre ne se justifiera que pour un débutant n'ayant aucune notion d'agilité. Chaque article est alors un bon point de départ pour s'interroger sur son expérience personnelle.
Enfin, voici les 3 conseils qui m'ont personnellement le plus interpelés :
* Ask, "What Would the User Do?" (You Are Not the User)
* Your Customers Do Not Mean What They Say
* Don't Just Learn the Language, Understand Its Culture
Technical part of the book is the one side of he coin, second one is the content. 97 Things' is a book that covers topics you can find in many other books (Pragmatic Programmer, Agile Developer, Developers Notebook, Productive Programmer). What distinguish this book is the way topics are presented. Authors do not go deeply into details, they just sketch the issue, provide readers with the starting point and don't give them 'silver bullet'. Many times you will fell like ' 'hey, I knew that already' ' but that's OK, because you started to think about the again. I liked the book, I liked the topics, however different style of each essay might be confusing a little bit. If you like consistent style over the whole book, this will be a drawback. Another thing is ' if you have read books like Pragmatic Programmer or Practices of an Agile Developer, rethink buying this book. You might feel disappointed. If you haven't read them ' it might be a good starting point for getting a better programmer.
J'ai pour ma part remis une xUnit en état, relifté mon processus de production d'exécutables avec des numéros de version correctes et repris la bonne habitude de faire une pause avent toute modification importante, afin de privilégier le "do it right from the first time".
Ceci justifie dans mon cas l'investissement.
Commentaires client les plus utiles sur Amazon.com (beta)
97 Things Every Programmer Should Know is a collection of short, two page essays, each by an experienced programmer. The book is a collection of tips and tricks for writing code that works, that is maintainable both by the author and by others, and that will best fit the situation. While the book doesn't measure up to some of my all time favorites in the genre like The Art of Unix Programming or The Pragmatic Programmer, it wasn't meant to. This is not an in depth guide to underlying philosophies of coding practices and standards, but quick hit and run articles that would be easy to fully grasp and absorb in short five minute bursts, such as during work or study breaks (which is how I read the book).
Some of the topics included in this book will seem obvious such as "Don't Ignore That Error" and "Comment Only What The Code Cannot Say," and some tips are going to serve only as reminders to best practices that are sometimes ignored (to our own peril) like "Check Your Code First Before Looking To Blame Others" and "Make Interfaces Easy To Use Correctly And Difficult To Use Incorrectly," there are some real gems in the book that aren't so obvious like one author's instruction to "Read the Humanities" because they are a great tool to help programmers learn to effectively interact with people and not just software and the advice that says "Don't Just Learn the Language, Understand Its Culture" so that you will write effectively and idiomatically within each language, rather than writing the same thing using different words.
I can't say that this is a must-have book for experienced programmers, but anyone at the novice to intermediate levels would certainly benefit from what the book contains. I've enjoyed reading it.
Speaking of which, where is the code? A book on programming without code is like a day without sunshine! To give one example: The second essay, "Apply Functional Programming Principles" by Edward Garson, assures you that you'll write cleaner, clearer code after working with a functional programming language, but his assurances feel awfully airy without any examples. Maybe this is inevitable in a book that's language-agnostic. Books like Code Complete and Clean Code are hopping with code samples (in C++ and Java, respectively); as a result, they do a far better job of engaging the reader and making abstract concepts stick.
A notable exception is "Code in the Language of the Domain" by Dan North, which uses code to illustrate a concept and uses it well. You might want to read that one, but you don't need to buy the book to do so: All of the essays in this book are Creative Commons-licensed and can be read on the book's official website.
Here is why Joel Spolsky's books are so good: He tells stories. He gives examples. He restrains himself from bombarding the reader with familiar aphorisms. You're imbibing his experiences, not just listening to him ramble. If you haven't already read Joel on Software and More Joel on Software, definitely do so. Also check out the deep interview collection Coders at Work. It's the 98th thing every programmer should know.
I found essays like "How to Implement Doing it Right vs Getting it Done" to be very helpful and wise. That essay included pratical advice that we were able to apply by changing our design for our in house bug tracking software to include a technical debt tracker. "Coding with Reason" included some decent maxims that I hope my programmers implement, and I will be checking for in future code reviews. It is for these excellent essays among others that the book is worth reading.
As a software development manager who also gets involved in the business side of things I was amused at how occasionally at the contradiction that exist between the business world and the software development world. In the essay "The Professional Programmer" that emphasized among other things that programmers should not tolerate bug lists and take responsibility for training themselves (I agree). However, I know that often times programmers have little control over their time and I know that our fallen nature inclines people who self study (if they do it all) often times to study what they like rather than what is useful to the company. In my knowledge of Business management the opposite advice is given, that in order to keep a motivated workforce the employer needs to provide training and/or training opportunities. Essays pushing pair programming made a good argument for it, but excluded what practical ideas can be implemented if such a thing is not possible.
Sometimes I did not always agree with all the essays nor did I think that certain maxims should be elevated to the level of dogmas. Where the book suffered was that some of the essays selected seemed to reiterate points that where already made in other essays.
I would recommend this book and I will even be using it for our in house book club.
What do you get when you get 97 tidbits of hard-learned experience? Some great insight to learn from other's experiences.
This is a good casual read that can be done in two hours. Since all the articles are short, it can be read in quick phases. It also can spark your interest in certain topics to go find full books on it.