Slimmer wonen
€ 9,18

Promoties zijn van toepassing bij aankoop

Deze aanbiedingen worden op dit artikel toegepast:

Sommige promoties kunnen worden gecombineerd; anderen komen niet in aanmerking om te worden gecombineerd met andere aanbiedingen. Voor meer informatie, zie de voorwaarden die zijn gekoppeld aan deze promoties.

Prijs is inclusief btw
Verkocht door Amazon Media EU S.à r.l..
Je bent geabonneerd op ! We zullen je items vooruitbestellen binnen 24 uur nadat ze beschikbaar zijn. Wanneer nieuwe boeken worden uitgebracht, brengen we je de laagste prijs die beschikbaar is in rekening tijdens de vooruitbestellingsperiode bij jouw standaard betaalmethode.
Werk je apparaat of betaalmethode bij, annuleer afzonderlijke vooruitbestellingen of je abonnement bij
Je lidmaatschappen en abonnementen
Toegevoegd aan

Sorry, er is iets misgegaan.

Er is een fout opgetreden bij het ophalen van je verlanglijsten. Probeer het nog eens.

Sorry, er is iets misgegaan.

Lijst niet beschikbaar.
Afbeelding van logo voor Kindle-app

Download de gratis Kindle-app en begin direct Kindle-boeken te lezen op je smartphone, tablet of computer. Geen Kindle-apparaat vereist.

Lees direct in je browser met Kindle voor Web.

Gebruik de camera van je mobiele telefoon om de onderstaande code te scannen en de Kindle-app te downloaden.

QR-code voor downloaden van Kindle-app

  • Naming Things: The Hardest Problem in Software Engineering (English Edition)

Naming Things: The Hardest Problem in Software Engineering (English Edition) Kindle-editie

Engelstalige uitgave Tom Benner (auteur) Indeling: Kindle-editie
4,2 van 5 sterren (120)
Naming is one of the most difficult and enduring challenges in software engineering, but few of us do it well. This practical and comprehensive book provides a set of principles, rules, and application guidelines for efficiently choosing good names in your code.

These skills can be used throughout your career, and they’re useful for every programming language, technical domain, and experience level. The book incorporates real-world examples to illustrate how to choose good names and avoid bad names.

This book includes:
  • Rules for how to choose good names and avoid bad names
  • Principles to help you remember the general qualities of good names
  • Real-world examples
  • Guidelines on the application of these rules and principles, including balancing tradeoffs, renaming best practices, and choosing domain-specific names
  • Tips on how to develop your naming skills throughout your career

Changes in the second edition:
  • Improved conciseness
  • Removal of less important content
  • Grammatical improvements
  • Formatting improvements
Meer lezen
Vorige dia met productgegevens
  1. Printlengte
    100 pagina's
  2. Taal
    Engels
  3. toegankelijkheid
    Meer informatie
  4. Publicatiedatum
    24 januari 2023
  5. Bestandsgrootte
    3.3 MB
  6. Bladeren
    Ingeschakeld
  7. Word Wise
    Niet ingeschakeld
  8. Verbeterd lettertype
    Ingeschakeld
Volgende dia met productgegevens

Veiligheids- en productbronnen

Afbeeldingen en contactpersonen

Veiligheidsbeelden en contactpersonen

Productgegevens

  • ASIN ‏ : ‎ B0BT15GFZG
  • toegankelijkheid ‏ : ‎ Meer informatie
  • Publicatiedatum ‏ : ‎ 24 januari 2023
  • Editie ‏ : ‎ 1e
  • Taal ‏ : ‎ Engels
  • Bestandsgrootte ‏ : ‎ 3.3 MB
  • Schermlezer ‏ : ‎ Ondersteund
  • Verbeterd lettertype ‏ : ‎ Ingeschakeld
  • X-Ray ‏ : ‎ Ingeschakeld
  • Word Wise ‏ : ‎ Niet ingeschakeld
  • Printlengte ‏ : ‎ 100 pagina's
  • Bladeren ‏ : ‎ Ingeschakeld
  • Plaats in bestsellerlijst: #956 in Softwaredesign, -tests & -engineering
  • Klantenrecensies:
    4,2 van 5 sterren (120)

Klantenrecensies

4,2 van 5 sterren
120 wereldwijde beoordelingen

Beste recensies uit andere landen

Vertaal alle beoordelingen naar het Nederlands
  • Kevin Jerome
    3,0 van 5 sterren Good yet shallow advice
    Beoordeeld in Canada op 7 juni 2024
    Formaat: PaperbackGeverifieerde aankoop
    This book is shallow, both in the number of pages and the depth of the content.

    It's not bad per se, but it's mostly common sense or well-trodden ideas put to paper. If you've been programming for several years, none of this advice will surprise you.

    The advice is not always well-motivated, often being heavily opinionated without referring to any data to back it up. This is fine for some people, but I would have preferred case studies or other forms of objectivity to have been introduced.

    The print quality was ok, but the book feels flimsy and the cover is easily stained from touches.

    I wouldn't spend too much on this book if you're looking to get it. You can easily find similar content online.
    Melden
  • Karl Vogel
    5,0 van 5 sterren Good advice in a small package
    Beoordeeld in de Verenigde Staten op 18 november 2025
    Formaat: PaperbackGeverifieerde aankoop
    I was originally going to give it 4 stars for being too short until I remembered that I don't like authors who bloviate or pad their stuff to make it look bigger.

    The book has most of the useful naming advice all in one place.
    Melden
  • Blackmagic
    5,0 van 5 sterren Simple book which is quite helpful.
    Beoordeeld in Duitsland op 3 augustus 2023
    Formaat: PaperbackGeverifieerde aankoop
    The content seems obvious when you read it but its quite helpful to clarify the way you write code.
    I would recommend it if you're a software professional.
    Melden
  • Esteban A. Maringolo
    4,0 van 5 sterren Concise with a good set of guidelines
    Beoordeeld in de Verenigde Staten op 13 februari 2025
    Formaat: Kindle-editieGeverifieerde aankoop
    The book approaches the problem of naming things in the context of software development. As somebody who prides in having named lots of classes and method, I found this reassuring on the importance of using the right names and abstractions, as it's not just a software artifact, but also helps in the understanding of the problem or domain you and your team (or the whole company) tries to solve.

    If you suck at naming, this will be a five star book, if you are good at naming things, this will be more of a checklist and a nice walk through the problem of naming things.
    Melden
  • David Bakin
    5,0 van 5 sterren Rules you know organized into 4 principles that help you remember them and use them
    Beoordeeld in de Verenigde Staten op 23 juli 2023
    Formaat: Kindle-editieGeverifieerde aankoop
    This thin book, if read by software engineers, and taken to heart, would improve code quality everywhere. Just naming things properly is an incredible way to write correct code in the first place, or improve it when you find problems.

    And it really is the hardest problem in software engineering - it's so hard to even name things at all that coders will do things they know are wrong to avoid it: long long methods with all code inline, class names that are just some noun with "Manager" or "Factory" or "Processor" or "Action" tacked on to the end as if that was sufficient to let you know what was going on, throwaway names that don't describe the entity named, not changing test names to reflect changes in the test (many times the test name doesn't even accurately state what the test is testing!), etc. etc.

    Yet I have found over and over that naming things properly - and breaking things out and giving them a name - contributes significantly to correctness.

    The most obvious way is that a correct name breaks the connection between one section of code and another section - especially if that other section would be embedded in the first one if you didn't break it out to give it a name.

    * You start with the named thing: you read the name, understand what it is supposed to do, then you read the code there, locally, and decide if it does what the name says it does.
    * Now you go back to where the name is used - you know the name accurately describes what's going to happen so you can consider it's use right there without referring again to the code behind it.

    Another way proper naming works well is if you name things in such a way that uses of the name in conditionals makes everything simpler.
    * This is why in code reviews I constantly point out that expressions used in conditionals should be:
    * Broken out into a named predicate (even if only a local Predicate - maybe especially then)
    * And that the predicate name should be positive
    * Because IMO it leads to much easier to understand boolean-valued expressions

    In 30 short pages this book lists the rules you need to follow to name things properly. And you've probably heard each on of rules principles before, one at a time. The value of the book is that these rules are organized into 4 principles and explained together in a way that it all hangs together, and then the principles - and many of the rules - stick in you mind, where you can have them ready when you need to name something.

    There's another 30 pages on how to apply the principles/rules in various settings.

    $10 on Kindle and well worth it. Even pay the extra $5 and get it in paperback - it's small and thin and very easy to flip through to refresh your understanding with.
    Melden
Bekijk meer recensies

Probleem melden


Bevat dit item ongepaste content?
Melden
Denk je dat dit item in strijd is met een auteursrecht?
Melden
Bevat dit item kwaliteits- of opmaakproblemen?
Melden