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.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.

Prix Kindle : EUR 15,30

Économisez
EUR 15,83 (51%)

TVA incluse

Ces promotions seront appliquées à cet article :

Certaines promotions sont cumulables avec d'autres offres promotionnelles, d'autres non. Pour en savoir plus, veuillez vous référer aux conditions générales de ces promotions.

Envoyer sur votre Kindle ou un autre appareil

Envoyer sur votre Kindle ou un autre appareil

Repliez vers l'arrière Repliez vers l'avant
Narration Audible Lecture en cours... Interrompu   Vous écoutez un extrait de la narration Audible pour ce livre Kindle.
En savoir plus

97 Things Every Programmer Should Know: Collective Wisdom from the Experts Format Kindle

3.3 étoiles sur 5 3 commentaires client

Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
EUR 15,30

Longueur : 255 pages Langue : Anglais

Ponts de mai 2016 Promo Ponts de mai 2016


Descriptions du produit

Présentation de l'éditeur

Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.

With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you can apply to all kinds of projects.

A few of the 97 things you should know:

  • "Code in the Language of the Domain" by Dan North
  • "Write Tests for People" by Gerard Meszaros
  • "Convenience Is Not an -ility" by Gregor Hohpe
  • "Know Your IDE" by Heinz Kabutz
  • "A Message to the Future" by Linda Rising
  • "The Boy Scout Rule" by Robert C. Martin (Uncle Bob)
  • "Beware the Share" by Udi Dahan

Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 1217 KB
  • Nombre de pages de l'édition imprimée : 258 pages
  • Utilisation simultanée de l'appareil : Illimité
  • Editeur : O'Reilly Media; Édition : 1 (5 février 2010)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B0039OVIAK
  • Synthèse vocale : Activée
  • X-Ray :
  • Word Wise: Non activé
  • Composition améliorée: Non activé
  • Moyenne des commentaires client : 3.3 étoiles sur 5 3 commentaires client
  • Classement des meilleures ventes d'Amazon: n°266.950 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Voulez-vous faire un commentaire sur des images ou nous signaler un prix inférieur ?

Commentaires en ligne

3.3 étoiles sur 5
5 étoiles
0
4 étoiles
1
3 étoiles
2
2 étoiles
0
1 étoiles
0
Voir les 3 commentaires client
Partagez votre opinion avec les autres clients

Meilleurs commentaires des clients

Format: Broché
"97 Things Every Programmer Should Know" est un livre pour accompagner le développeur dans son parcours initiatique sans cesse renouvelé. Programmer est un art et comme tout art, il a ses codes qu'il faut savoir respecter ou transgresser à bon escient. Ce livre présente 97 brefs articles qui sont autant d'opportunités de s'interroger sur notre façon de programmer.

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
Remarque sur ce commentaire 4 personnes ont trouvé cela utile. Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus
Format: Broché
What I have liked from the very beginning of the book, was the way the content description was organized. There are two tables of content ' first one, regular one, second one divides book into different categories, thus you can read just essays related to particular topic. Another great advantage of the book is the way essays were prepared ' two pages per each of them. No wasted space, no elaborates, just the core of the problem that is discussed. The same thing refers to the index ' I like books where you can find things within index easily and accurately.

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.
Remarque sur ce commentaire Une personne a trouvé cela utile. Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus
Format: Broché
Sans véritable ambition autre que de rafraîchir la mémoire d'un spécialiste, ce livre se lit facilement, en petite phases, quelques pages par-ci par-là. C'est la meilleure façon on pas d'apprendre (vous n'allez pas découvrir énormément de nouveautés) mais plutôt de faire le point ou de se rappeler que quelques pratiques, jointes à une saine discipline peuvent vous simplifier la vie.

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.
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: HASH(0x8efca18c) étoiles sur 5 40 commentaires
35 internautes sur 35 ont trouvé ce commentaire utile 
HASH(0x8f006684) étoiles sur 5 Great bathroom or bus commute reading for programming beginners 22 mars 2010
Par M. Helmke - Publié sur Amazon.com
Format: Broché
I have read programming books for years. There was a time when I could write a "Hello World" program in each of seven or eight languages. That time has passed, mainly because I haven't been intimately involved in any specific software project for many years. Still, I have this habit of reading programming books and enjoying them, perhaps in the hope or expectation that one of these days I'll find myself with a project in front of me, time to work on it, and motivation to learn a new language or tool to make the project's vision a reality. Well, here's the newest book of programming foundational tips that I have read.

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.
60 internautes sur 67 ont trouvé ce commentaire utile 
HASH(0x8f008360) étoiles sur 5 Abstract and aphoristic 21 février 2010
Par Trevor Burnham - Publié sur Amazon.com
Format: Broché
If you're just entering the programming world, this collection of 2-page essays might be a useful resource. But if you've been reading programmer blogs for a while, or you've worked on a couple of projects, then there's little of value here. Very few of the essayists choose to tell stories; instead, they say things like "Remember that humans always make mistakes," "Read other people's code" and "Always leave the campground cleaner than you found 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.
4 internautes sur 4 ont trouvé ce commentaire utile 
HASH(0x8f008f90) étoiles sur 5 A Starting Point For Your Conversations 17 mars 2010
Par Michael T. Fisher - Publié sur Amazon.com
Format: Broché Achat vérifié
This book is a compilation of short essays ranging on topics as diverse as Bugs, Error Handling, Customers, Refactoring, and Expertise. The purpose of the short essay is not to answer all your questions or be a definitive guide to programming. Rather the purpose is to provide a starting point for a conversation. To this end, I think a practical way to use this book whether in academia or a development team would be to assign groups of essays to be read ahead of time to stimulate classroom or team meeting discussions. Read my full review of the book here,
[...].
2 internautes sur 2 ont trouvé ce commentaire utile 
HASH(0x8f008f78) étoiles sur 5 Some Beneficial Advice and Maxims 9 octobre 2013
Par Noah Moerbeek - Publié sur Amazon.com
Format: Broché Achat vérifié
97 things every programmer should know is a light easy read that is broad enough to appeal to anyone who works in code or on software projects in general.

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.
2 internautes sur 2 ont trouvé ce commentaire utile 
HASH(0x8f00e360) étoiles sur 5 Better than the other 97 things books 17 novembre 2011
Par David - Publié sur Amazon.com
Format: Broché
Just like all of this series, these are free articles that can be found online, so if you what the hard copy, I recommend buying it used. The steep price is most likely just the publisher taking a huge cut, and I'd much rather pay the people who wrote it.

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.
Ces commentaires ont-ils été utiles ? Dites-le-nous

Discussions entre clients