لطفا منتظر باشید ...
The Developer's Notebook Series
So, you've managed to pick this book up. Cool.
Really, I'm excited about that! Of course, you may
be wondering why these books have the odd-looking, college notebook
sort of cover. I mean, this is O'Reilly, right?
Where are the animals? And, really, do you need
another series? Couldn't this just be a cookbook?
How about a nutshell, or one of those cool hacks books that seems to
be everywhere? The short answer is that a
developer's notebook is none of those
thingsin fact, it's such an important idea
that we came up with an entirely new look and feel, complete with
cover, fonts, and even some notes in the margin. This is all a result
of trying to get something into your hands you can actually use.
It's my strong belief that while the nineties were
characterized by everyone wanting to learn everything (Why not? We
all had six-figure incomes from dot-com companies), the new
millennium is about information pain. People don't
have time (or the income) to read through 600 page books, often
learning 200 things, of which only about 4 apply to their current
job. It would be much nicer to just sit near one of the uber-coders
and look over his shoulder, wouldn't it? To ask the
guys that are neck-deep in this stuff why they chose a particular
method, how they performed this one tricky task, or how they avoided
that threading issue when working with piped streams. The thinking
has always been that books can't serve that
particular needthey can inform, and let you decide, but
ultimately a coder's mind was something that
couldn't really be captured on a piece of paper.
This series says that assumption is patently wrongand we aim
to prove it.
A Developer's Notebook is just what it claims to be:
the often-frantic scribbling and notes that a true-blue alpha geek
mentally makes when working with a new language, API, or project.
It's the no-nonsense code that solves problems,
stripped of page-filling commentary that often serves more as a
paperweight than an epiphany. It's hackery, focused
not on what is nifty or might be fun to do when
you've got some free time (when's
the last time that happened?), but on what you need to simply
"make it work." This
isn't a lecture, folksit's a
lab. If you want a lot of concept, architecture, and UML diagrams,
I'll happily and proudly point you to our animal and
nutshell books. If you want every answer to every problem under the
sun, our omnibus cookbooks are killer. And if you are into arcane and
often quirky uses of technology, hacks books simply rock. But if
you're a coder, down to your core, and you just want
to get on with it, then you want a Developer's
Notebook. Coffee stains and all, this is from the mind of a developer
to yours, barely even cleaned up enough for print. I hope you enjoy
it...we sure had a good time writing them.
