The Productive Programmer (Theory in Practice (O'Reilly)) 1st Edition, Kindle Edition
Use the Amazon App to scan ISBNs and compare prices.
- Highlight, take notes, and search in the book
- Length: 226 pages
The Amazon Book Review
Discover what to read next through the Amazon Book Review. Learn more.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
Top Customer Reviews
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.
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.
While I don't like giving negative reviews, I figured it would be useful to other potential readers to give a no-fluff review of the book -- here we go:
This book is a decent book for new programmers. If you're fresh out of college, and have never before done any sort of real programming work, you'd likely find this book a quick and review-ish read. Most of the content of this book is extremely obvious stuff, I could summarize most of the book by stating the following points:
- Optimize your computer to get work done (use hotkeys, learn your editor well).
- Automate boring stuff that wastes times (running Excel reports, etc.).
- Focus on what you're working on and try to maintain flow.
The above three points are discussed and primarily talked about in the first 1/2 of the book. The rest of the book is dedicated to well known programming principles which I won't get into here -- suffice to say, if you're a programmer, you've likely already heard of and used them.
For any experienced developer, this book feels... Like a recipe. It comes off (to me) as being a well planned book with good intentions, but that (unfortunately) ends up covering a seemingly small array of things and only lightly touching on each subject. While other great books like The Pragmatic Programmer spend a lot of time covering productivity principles in great detail, this book seems to skimp on the content and focus on brevity in less less interesting topics.
While I really wanted to love this book (I'm a junkie when it comes to programming productivity stuff), I simply can't recommend this book to anyone but new developers looking for a quick read.
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.
Most Recent Customer Reviews
When I start working as a Software Developer (late 90s) there were not so many books that talked about what it takes to be a good and productive...Read more
I received a free e-copy of this book through O'Reilly [Blogger Review Program]([...Read more
Set up an Amazon Giveaway
Look for similar items by category
- Books > Computers & Technology > Computer Science
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Object-Oriented Design
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Programming Languages
- Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Development