Read, read, read. Read everything - trash, classics, good and bad, and see how they do it. Just like a carpenter who works as an apprentice and studies the master. Read! You'll absorb it. Then write. If it is good, you'll find out. If it is not, throw it out the window.
-
William Faulkner
About / Biography
Resume
Contact
Journal / Blog
Recommended Reading
Reviews
View Adam Kahtava's profile
Recent entries
Categories
.NET
AJAX
ASP.NET
ASP.NET AJAX
ASP.NET MVC
BarCamp
Book
C++
Calgary
Career News
Code Camp
Community
Contest
Creativity
CSharp
CSS
dasBlog
DOM
Ergonomics
Events
Firebug
Firefox
greasemonkey
IE
Interview
JavaScript
Links
Merb
Musings
Open Source
Opera
Ottawa
Personal
PowerShell
Programming Languages
Quality Assurance
Review
RoR
Software
Team Work
Themes and Skins
Toronto
Twitter
Unit Testing
Videos
XML
Archives
December, 2008 (4)
November, 2008 (6)
October, 2008 (10)
September, 2008 (8)
August, 2008 (2)
July, 2008 (4)
June, 2008 (7)
May, 2008 (6)
April, 2008 (8)
March, 2008 (7)
February, 2008 (3)
January, 2008 (1)
December, 2007 (1)
November, 2007 (2)
October, 2007 (1)
September, 2007 (3)
July, 2007 (1)
May, 2007 (3)
April, 2007 (4)
March, 2007 (4)
February, 2007 (5)
January, 2007 (3)
December, 2006 (1)
November, 2006 (5)
October, 2006 (6)
September, 2006 (8)
August, 2006 (2)
July, 2006 (8)
June, 2006 (9)
May, 2006 (1)
Syndicate this site
Sign In
powered by
dasBlog
Journal / Blog
Wednesday, April 16, 2008
How To Choose a Good Technical Book
The quality of technical books have wide variations between publishers and authors. While choosing a book based on the author
is
reliable, depending on a publisher or brand name
is not
reliable, and choosing a book based on advertisements is even less reliable. It makes sense to choose your books wisely since most technical books live a short life (the duration of a single project), cost money, and require precious time to be read.
When choosing a book I follow this heuristic approach:
Ask experts in the field (friends, forums, newsgroups) for recommendations
Ask these experts to differentiate between the high level books and the books that take a technical deep dive.
Filter out (discard) the high level recommendations.
Filter out (discard) all recommendations that contain the following keywords in their title:
Cookbook
Problem - Design - Solution
Hacks
Tips
Learn X in 24 hours
Look for recognizable authors.
Cross reference these recommendations through Amazon's Reviews:
Books with over 100 excellent ratings on Amazon are instant winners - the Amazon community is rarely misleading.
Books that haven't received more than 50 ratings should be considered with skepticism - visit a local book store and skim through the text in question before making the purchase.
Book
|
Musings
|
Software
PermaLink
|
Digg It
|
Del.icio.us
|
Comments [0]
Related posts:
The Best Teacher I Ever Had: An Ode to Stephan Regoczei
I WANT MEANS if I want it enough I will get it.
Bad Advice: If you don't have anything nice to say, don't say anything at all
Passion, Quality Over Quantity, Domestic Failure: Microsoft, Ford, GM, Chrysler?
Do Great Developers Cluster Away From Microsoft?
Blogs, Facebook, Twitter, the Internet, ... are White Noise
Name
E-mail
Home page
Remember Me
Comment (Some html is allowed:
a@href@title, b, blockquote@cite, i, img@src, strike, u
) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.
Enter the code shown (prevents robots):
Live Comment Preview
Page rendered at Friday, December 05, 2008 12:48:44 PM (GMT Standard Time, UTC+00:00)
Disclaimer & Copyright
© 2008
Adam Kahtava
(
Adam.Kahtava.com
/
AdamDotCom.com
)
:: Friday, December 05, 2008 12:48:44 PM (GMT Standard Time, UTC+00:00)