- Taschenbuch: 141 Seiten
- Verlag: O'Reilly UK Ltd.; Auflage: 1 (1. Februar 2012)
- Sprache: Englisch
- ISBN-10: 1934356794
- ISBN-13: 978-1934356791
- Größe und/oder Gewicht: 15,2 x 1,3 x 22,9 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 288.307 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
The Developer's Code (Englisch) Taschenbuch – 1. Februar 2012
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
This is the next "Pragmatic Programmer"--a guide for the beginner, a reminder for the expert, and a wonderful chunk of wisdom about the craft (and life) of a developer.--Derek Sivers Founder of CD Baby, sivers.org Ka Wai Cheung has written a book for professional developers seeking a code they can live by. This is not a book replete with conventional, find-it- in-any-blog ideas but a very powerful, focused approach to the craft and realities of professional programming. If you are looking for a rehash of stale, sterile rules for programming, this is not the book for you. But if you are seeking a perspective on what creating software is, or if you want a set of guidelines laden by real-world experience, this is a book you need.--Bob Walsh Author and Founder of 47 Hats Packed with delicious lessons yet consumable in bite (byte?) sized chunks --there's a lot to be learned in these pages. Take some time and learn from someone who's been there.--Adam Hoffman Senior Development Lead
Über den Autor und weitere Mitwirkende
Ka Wai Cheung is a developer, designer, and founding partner at We Are Mammoth, an award-winning team of web developers as passionate about approachability as they are about technology. Ka Wai is also the co-author of Flash Application Design Solutions: The Flash Usability Handbook.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
The book is divided into 52 sections (the last two of which haven't been numbered), with titles like "Lie to Simplify," "Invest in a Good Work Environment," "Work Outside the Bedroom," and "Teach with Obvious Examples." It can't be said there are earth-shattering insights in these sections.
Chapter 4 on productivity presented a great idea on how to take "Ta-Da", the free to-do list progam from 37 Signals one step higher. The author's simple technique in Essay 22 has already helped me to better track my accomplishments. Chapter 9, entitled "Pride" was a real pleasure to read. I liked how he explained the phenomena of the cooking-show industry, how its changed over the years, and how software development should use this as a marketing idea. The chapter also talked about "The Healing Power of Construction Work" and how developers fall into the same boat as construction workers, namely, that software development is therapeutic.
In summary, it was a great book to read on my Kindle and reminded me of things I learned in the past but have forgotten.
None of the essays here (52 in total) are technical in nature. You won't learn a new way to code algorithms or do systems architecture. Instead, they delve into mind-sets and concepts on how to think about the work and how it's done. An example would be the first two essays in the section on metaphors in software development. Since we've equated software construction to building construction, we tend to over-plan a system and nail everything down before we write a single line of code. But in reality, code is flexible and changeable, whereas bricks and mortar can't be easily "fixed" once it's put down. The metaphor of "construction" means that we may over-plan before writing code (think waterfall vs. agile), thereby limiting our productivity. Metaphors aren't bad, but you do need to be careful that it doesn't inadvertently create boundaries that don't exist.
I personally found the section on teaching fascinating. Specifically, "Lie to Simplify" put words behind a problem I fall prey to on far too many occasions. When trying to teach someone a new skill or feature, I want to tell them absolutely everything... all the edge cases, the minor oddities, and the obscure errors where things don't work as advertised. The problem is that the student doesn't even understand the basic concepts, much less the esoterica. Rather than dump everything on them at once, just lie. Tell them how things work in 95% of the situations. Don't even mention the exceptions... until they've mastered the basics. Once they know that knowledge, you can fill in the blanks. That single essay right there will change the way I convey information to others.
Since everyone comes from different backgrounds and experience levels, everyone will have different reactions to The Developer's Code. But I think I'm safe in saying it's well worth reading, and you should easily find the two or three gems that will make your purchase a wise investment in yourself.
Introduction: Who Is the 21st-Century Programmer?; Discovering the Lessons Firsthand; This Book Is About Us
Metaphor: Follow Metaphors with Care; Plan Enough, Then Build; Launch Is Just the First Release; The "Ivory Tower" Architect Is a Myth; Throw Away Your Old Code; Diversification Over Specialization; Metaphors Hide Better Ways of Working
Motivation: The Perks Are in the Work; Begin Where You Love to Begin; Be Imperfect; Stop Programming; Test Your Work First Thing in the Morning; Work Outside the Bedroom; First Impressions Are Just That; The Emotional Value of Launch; Find an Argument
Productivity: Just Say "No" to the Pet Project; Constrain All of Your Parameters; Cut the Detail Out of the Timeline; Improve Your Product in Two Ways Daily; Invest in a Good Work Environment; Keep a Personal To-Do List; Create "Off-Time" with Your Team; Work in Small, Autonomous Teams; Eliminate the "We" in Productivity
Complexity: Sniff Out Bad Complexity; The Simplicity Paradox; Complexity as a Game of Pickup Sticks; Keep Complexity Under the Surface; "Hard to Code" Might Mean "Hard to Use"; Know When to Refactor; Develop a Programming Cadence
Teaching: Teaching Is Unlike Coding; Beware the "Curse of Knowledge"; Teach with Obvious Examples; Lie to Simplify; Encourage Autonomous Thought
Clients: The Tough Client Is Ubiquitous; Demystify the Black Magic of Software; Define the Goals of Your Application; Be Enthusiastic and Opinionated; Be Forgiving and Personable; Value Is Much More Than Time; Respect Your Project Manager
Code: Write Code As a Last Resort; A Plug-in Happy Culture; Code Is the Ultimate Junior Developer; Separate Robot Work from Human Work; Generating Code at Its Core; The Case for Rolling Your Own
Pride: We Have a Marketing Problem; Lessons from the Cooking Industry
Obtained From: Publisher
If you are a serious life-time engineer who wants a little pick-me-up to get back into fun development buy this book.
In other words, if you want some scattered biographical facts from a web developer along with some worn-out advice and don't mind spending 2-3 hours, you can have a try at it. Unfortunately, I cannot sincerely recommend this short book to anyone.