|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Frequently Bought Together
Product Details
|
Product Description
Product Description
Anyone who develops software for a living needs a proven way to produce it better, faster, and cheaper. The Productive Programmer offers critical timesaving and productivity tools that you can adopt right away, no matter what platform you use. Master developer Neal Ford not only offers advice on the mechanics of productivity-how to work smarter, spurn interruptions, get the most out your computer, and avoid repetition-he also details valuable practices that will help you elude common traps, improve your code, and become more valuable to your team. You'll learn to:
- Write the test before you write the code
- Manage the lifecycle of your objects fastidiously
- Build only what you need now, not what you might need later
- Apply ancient philosophies to software development
- Question authority, rather than blindly adhere to standards
- Make hard things easier and impossible things possible through meta-programming
- Be sure all code within a method is at the same level of abstraction
- Pick the right editor and assemble the best tools for the job
This isn't theory, but the fruits of Ford's real-world experience as an Application Architect at the global IT consultancy ThoughtWorks. Whether you're a beginner or a pro with years of experience, you'll improve your work and your career with the simple and straightforward principles in The Productive Programmer.
About the Author
Neal is an Application Architect at ThoughtWorks, a global IT consultancy with an exclusive focus on end-to-end software development and delivery. Before joining ThoughtWorks, Neal was the Chief Technology Officer at The DSW Group, Ltd., a nationally recognized training and development firm. Neal has a degree in Computer Science from Georgia State University specializing in languages and compilers and a minor in mathematics specializing in statistical analysis. He is also the designer and developer of applications, instructional materials, magazine articles, video presentations, and author of the books Developing with Delphi: Object-Oriented Techniques (Prentice-Hall, 1996), JBuilder 3 Unleashed (Sams, 1999) (as the lead author), Art of Java Web Development (Manning, 2003), and No Fluff, Just Stuff Anthology: The 2006 Edition (editor and contributor). His language proficiencies include Java, C#/.NET, Ruby, Object Pascal, C++, and C. His primary consulting focus is the design and construction of large-scale enterprise applications. Neal has taught on-site classes nationally and internationally to all phases of the military and to many Fortune 500 companies. He is also an internationally acclaimed speaker, having spoken at numerous developer conferences worldwide.If you have an insatiable curiosity about Neal, visit his web site at http://www.nealford.com. He welcomes feedback and can be reached at nford@thoughtworks.com.
Inside This Book
(Learn More)
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
2 of 2 people found the following review helpful:
4.0 out of 5 stars
Productivity made interesting,
By
This review is from: The Productive Programmer (Paperback)
When I first read about this book, it sounded too much like the Pragmatic Programmer. However, it turns out the books are very different.
The book feels like a collection of almost unrelated essays. This can make it seem a bit disjointed at times, but it also means you can read it in almost any order. I also bought the Windows Power Tools book and would recommend the Productive Programmer over that book. They don't cover the same ground, but a compact book that mentions really useful tools that won't date as quickly is better than a huge book of tools with very little detail about each. Neal Ford's writing style is concise yet fun and interesting. Examples are given using a variety of platforms and languages which is really unusual in a book - and he pulls it off without it becoming distracting.
5.0 out of 5 stars
Productivity increased,
By Touchstones wit (Calgary, AB) - See all my reviews
This review is from: The Productive Programmer (Paperback)
This book is chock full of useful tips both in terms of concrete solutions and high level approach to software creation. I especially appreciated Neal's learned yet down to earth tone, as well as the dash of humor he throws in for good measure. Lots of links to useful downloads and further reading. Read it while the links are still live!
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
4.3 out of 5 stars (34 customer reviews) 17 of 17 people found the following review helpful:
5.0 out of 5 stars
Concise work for productive, common sense development,
By James Holmes "Co-Author 'Windows Developer Po... - Published on Amazon.com
This review is from: The Productive Programmer (Paperback)
This is a terrific book for boosting your productivity in two areas: how you work, and how you code.
The first section of the book, Mechanics, focuses on tools you can use to boost your productivity as you're working with your system. Ford launches off into an exploration of lots of little crazy tools that help you automate or ease repetitive tasks. You'll find lots of goodies from virtual desktops to shortcut tips/launchers, to using Ruby to script everything from splitting up SQL to automatically sorting your laundry and washing it for you.[1] All these little tools and tricks add up to drastic decreases in the amount of friction you're forced to suffer through while doing your daily job. Cutting this friction lets you focus on the job at hand, instead of trying to bend your environment to your will. The second section of the book, Practice, discusses ways to speed your development. There's an awful lot of goodness in this portion of the book, ranging from re-emphasizing critical aspects of object oriented programming, to object and method composition. Ford walks through a lot of great stories meant to get you to re-evaluate why you do things a certain way. The infamous Angry Monkeys story gets pulled out as an example, and Ford also concisely covers development principles like the Law of Demeter, Occam's Razon, and his Polyglot Programming meme. The book's concise, amazingly well written, and a definite must-have for your bookshelf. 20 of 23 people found the following review helpful:
4.0 out of 5 stars
The Mechanics of a Pragmatic Programmers daily work,
By Michael Hunger "jexp" - Published on Amazon.com
This review is from: The Productive Programmer (Paperback)
I've been reading Neal's blog for a while. So I've been looking forward to the book. (I even accidentally ordered it twice - one was the pre-buy at amazon, which I forgot about).
I spend the last two days reading the book and found it quite helpful. There are a lot of concrete tips and examples for immediate use and daily improvement of your mechanic skills. Many of the experiences regarding the effective use of the tools at hand that he describes are well known to me. I can't really understand how developers are not keen to improve their productivity. Neal's book is a good addition to the PragProgs masterpiece. It concentrates more on the mechanics and on some principles of productive software development. So the triad of values-principles-patterns got a son named mechanics. What I missed in the book was: * a comprehensive list of the notes at the end. * Christopher Alexanders appearance as one of the philosophers. * the notion of cheat sheets/refcards * references to Martin Odersky's Scala the scalable language * references to Kent Becks "Implementation Patterns" (especially in the SLAP section) As being a developer myself I was a bit disappointed by the quality of the examples (the solutions not the starting points) and a bit by the correctness of the text (typos). I spotted several errors, some bad designs and some uninformed choices even on the first read of the book. I'll post them to the errata page. Neals suggestion of an online repository of productive programmers tools, tips and mechanics is a great idea. I'd really like to join this effort. Michael http://creating.passionate-developers.org 12 of 14 people found the following review helpful:
4.0 out of 5 stars
Great book but not without faults,
By Markus Oehler "Software Developer" - Published on Amazon.com
This review is from: The Productive Programmer (Paperback)
I saw Neal the first time at DLW Europe. I'd like to check out the speakers online before deciding which talks to attend - the results were not positive at all; IT consultant (we've had our share at work) + spending lots of time speaking on conferences, that's a combination not likely to give me warm feelings. I still ended up in attending his talk because of lack of alternatives and thank god I did. Neal isn't only a great speaker but he also had something to say and the necessary experience and war stories to back it up. I ended up by attending every presentation of Neal plus - back at work - giving a presentation of his talks to my fellow co-workers.
Finding out that he now has written a book - I instantly had to read it. And the book is certainly a valuable read that I'll keep around as reference at least for a while. There's lots of great tips about tools, automation, ... that will certainly find their way into my professional life. However, it did not blow me off my feet. I've read "Pragmatic Programmer - From Journeyman to Master" before (a perfect book in my opinion) and this book does not quite measure up to it. The style is not as perfect - the information not as well-presented. However what I miss most is that Neal sometimes present a topic but then does not follow up with "How to get started" - most notably with "Polyglot Programming" and "Test driven design". I know that both topics are maybe out of scope of the book but then at least a reference to another book, website, ... would have been great. So even if I'm all psyched to up try to apply this principles now at my current projects, I know from past experience that adding new languages in any mix more often result in time wasted time because of integration issues... and how to start TDD on a project that's been going on for 15 years without any unit tests is beyond my imagination. Don't get me wrong - it's a great book and well worth the read; it just needs some polishing to get it to excellent... |
|
Listmania!
|
|
Look for similar items by category
- Books > Computers & Internet > Programming > Languages & Tools
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Object-Oriented Design
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > New & Used Textbooks > Computer Science & Information Systems > Object-Oriented Software Design
- Books > New & Used Textbooks > Computer Science & Information Systems > Programming Languages
- Books > New & Used Textbooks > Computer Science & Information Systems > Software Design & Engineering
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
