A Computer Book Author's Manifesto
by Kathy Sierra11/30/2004
Editor's Note: Kathy Sierra, a co-creator of O'Reilly's Head First series, recently posted this letter to the StudioB mailing list. We enjoyed it so much that we asked Kathy for permission to share it with the world at large.
"Java book sales during the bubble were 10x what they are today."
"Computer book sales dropped another 15 percent just between 2003 and 2004."
"Most computer book authors cannot support themselves by doing only books."
"Computer book authors are dropping out of books altogether. . . ."
"The good days of tech books are gone, and they probably aren't coming back."
I came late to this party. My first book is not even two years old. I missed the bubble, the good days, the time when sub-1,000 Amazon rankings meant *real money*. But just when I feel so lucky to have been invited (or maybe I crashed it, but whatever, I'm here), so many are gathering their things and heading home. Party's over. My computer book author friends are cynical, skeptical, burned out. So I have to ask, ". . . and everyone is okay with this??"
To my computer book author friends I ask, "You're giving up without a fight?"
Because I'm not. I just got here, and I have no intention of sitting back on my (teeny tiny) royalties, passively watching the continuing drop but doing virtually nothing to try to stop it. Am I clueless and naive enough to think that there *is* something that can be done? Hell yes. Do I know what that something is? Hell no. (And I'm definitely not stupid enough to think that I somehow know something that all the other, way more experienced folks don't. In fact, I'm hoping the seasoned pros will be more vocal here on what we can and should be doing.)
That's not the point. The point is not giving up. And I wonder why more authors, editors, publishers, agents, reviewers, etc. aren't banding together and asking, "What can we do?" I will not accept this as inevitable. I don't care about the "market forces" or any other indicators that point toward a still grimmer future for computer book sales. Because I don't think there's anyone who can say that we've done everything that can be done. Simply trying to steal one another's market share is not a long-term, healthy solution, yet that's pretty much where we're at right now.
Let's say, for example, that the simple answers do tell the whole story--that the majority of computer book sales are in lock step with tech jobs and the progress of technology, and that if there isn't much happening out there, there isn't a need to buy computer books. That sounds reasonable and logical. The conventional wisdom says, "If they aren't forced to learn something new for their jobs, they won't learn it (and thus won't buy a book about it)." I'll buy that.
Almost.
The part I don't agree with is the assumption that most people don't want to learn something new (at least in the computer world) unless they must, or unless the technology or software itself is new (including new versions of existing products). And while the research does seem to suggest that this has been the trend in tech book sales in the past, does this really reflect some intrinsic property of tech topics?
If we continue to see tech books as supporting jobs and work, perhaps the drop is inevitable. But since most of us are geeks, and (although debatable in my case) reasonably intelligent and curious, what if we shifted slightly toward emphasizing the inherent joy and passion in some of these topics. In other words, what if we moved away from, "You have to learn this, so here's a book that does it to death" and more towards, "You don't have to learn this, but come on, you know you want to."
What if we thought more like the entertainment industry instead of the serious IT industry? After all, people don't play computer games or watch movies because they must. They don't play golf, or poker, or snowboard because they must. They don't play chess for work. They don't download a dozen songs from iTunes because they must. They do it for pleasure, and in some cases, a pleasure that borders on addiction.
What if we stopped thinking about it from purely a serious work perspective and started thinking about how we could seduce people into wanting to learn new computer topics? And by "new," I don't mean new technologies, but simply "new to that reader." If computer books are less tied to work and more tied to play/hobby, or even better, to passion, could we breathe more life into this market? If there isn't a big demand for computer books right now, could we--the authors, editors, publishers--do something to stimulate that demand rather than sitting back and waiting for demand to return? Could we ourselves do something to help drive people back to our little corner of Barnes and Noble?
Yes, I know that there are a ton of computer books that already take this approach. And I also see that many of these books are selling. Everyone talks about how the Macintosh computer has such a tiny market share as an operating system, yet it occupies a much larger market share in terms of computer book sales. Look at the sales of books related to iLife; there are probably only two people on the planet whose career/job depends on knowing GarageBand, but people are starting to buy those books. How many people must know iPhoto? Jeez, people are buying books on the iPod, a device that's virtually brainless to operate.
So I'm not suggesting anything new, but I am suggesting that as a whole, maybe a shift in the direction of people's passion vs. employment could help. Because if we ask the question, "If people don't have to buy a book for work, what can we do to cause them to buy a book for some other reason?" the answer might be, "Get them excited about learning something they don't already know, even if that something is not a new technology, but simply new to them."
And for that, we have to find ways to not suck the life and joy and pleasure out of the topics, ways to make those topics both compelling and accessible. We have to make learning those things seem more like fun hobbies, and less like work or school. And that might mean trying to find the inherent fun in topics that haven't traditionally been seen that way. But that also means that we have to do some of the work of positioning those topics as cooler than people might have previously thought. In other words, we have to take responsibility for convincing people that the topics are interesting and cool. Sure, it's easy to have people see an iPod or GarageBand as a hobby, and Apple's doing all the positioning for us. But what about computer programming? Security? Networking? Spreadsheets? Could we make some of the geekier and more traditionally work-oriented topics at least appear more like hobbies? Could we single-handedly reposition some of these technologies ourselves--to make people want to learn them? If people don't perceive the need, can we help create the need?
I have no idea.
(I could spend the rest of my life and probably not come up with anything I personally think is cool about PowerPoint, yet I just visited a museum installation at the Eastman house in Rochester, New York, and sure enough, there was David Byrne's PowerPoint thing.)
I'm just suggesting that this make-these-things-cool-and-compelling is one idea out of an endless number of things that we could be trying to do instead of accepting the continuing decline. It might be a really lame idea that won't work for a thousand different reasons, that you've all already thought about and researched. I don't care about that. If I worried that my ideas were lame and useless, I'd never do anything at all, since most of my ideas *are* lame and useless, and as so many computer book authors love to tell me, "been there, done that." And I say, "And your point?" I'd rather fail, look stupid, and have to change my name than sit by and not try.
OK, so let's say that the idea I just mentioned will not work at all, and it's already been tried in every possible way. Some of you must have other ideas that would work to drive more computer book sales. Have we explored every possible distribution option? Have we revisited the look/feel/implementation of computer books? Have we really asked readers/customers/learners/users what they want? Because it seems like technical books today don't look very different from the way they looked 90 years ago, while almost everything else in the world has changed dramatically. Is the "joystick nation" ready for something different? Maybe it's not even books at all that they want. Maybe they want to "learn differently," even if they can't articulate how that should happen. Lynda Weinman sure seems to be selling a lot of video training, for example, and I've got a lot of email from people who wish they could learn Java on their iPods, although a spoken version of one my books would never work. . . .
People ask me why I care about this so much. Why not move on? After all, I'm a way better programmer than writer, and right now, my programming skills are more in demand than my book writing skills. I make a tiny fraction today as a book author of what I made as a full-time software developer, and I have pretty much zero talent for computer book writing.
I have no trouble answering that question, because I never forget the business that I am in. I am not in the computer book authoring business. I'm certainly not "a writer." I am in the business of changing people's lives. That some of my friends don't recognize this about themselves is sad and perplexing to me. Every computer book author I know has gotten thank-you letters and emails from readers whose lives they've touched. There is a butterfly effect here and surely you feel this yourself. You helped one guy learn a topic that saved a key customer from deserting his company, and that saved his job. Which means his kids got to stay in the same school instead of transferring when he had to move the family to a less-expensive neighborhood or city, etc. It just goes on and on. I like to fantasize that even if all I did was save one guy a day over what it would have taken him to figure out something without my book, that one day might be the key to something magical.
Perhaps what really inspired me to write this is that a few weeks ago, the co-manager of our technical book review team died suddenly during what he (and everyone) thought was a fairly routine, low-risk surgery. Philippe Maquet, a Java guru from Belgium, was a healthy, energetic, fun-loving guy in his early 40s, and he devoted nearly all of his waking hours to helping people learn and implement new technologies. He worked by day as a Java consultant with the Loop Factory, and by night and weekend as a forum moderator and technical reviewer of our books. He did not write books and was not interested in writing them. Yet he felt that simply being a reviewer was a powerful contribution to improving people's lives. He reminded us all the time that the reason he did this (and he donated 100% of the fees he was paid to a non-profit) was because improving the technical quality of a book was improving the lives of the readers. He believed that helping to make something more clear, and reducing errata, was a very noble cause. His friends and family probably thought he was crazy for thinking that, but when he died, his employer wrote to tell us that working on these books was one of the things he was most proud of in his life.
In our last book, we surprised him with an acknowledgement that said, "All three of the authors love him so much we want to marry him. . . ." He got the book three days before he died, and said that he could not find the words to describe how much it meant to him. The day he died, but before any us knew he was in any danger, a personal thank-you from Tim O'Reilly was sent to him. And although he died before it arrived, his family said that it would have been one of the highlights of his life. Not because it was from Tim O'Reilly, but because of how important he felt it was to be part of something that made people's lives a little better.
This is probably the cheesiest StudioB post ever made, but I hope I can hang on to that feeling of Philippe's and use it to keep remembering that what I do does make a difference. And I only hope that all of my computer book author friends can remember how much of a difference they have made in other people's lives. In fact, many of you on this list have made a difference in my life over the years, although I never bothered to write to tell you. That doesn't mean we should all try to eek out a living as full-time computer book authors, but rather that we keep trying to find creative ways to at least stay in the game.
So, maybe I'll have to learn to be happy living on Rice-A-Roni and cheap coffee, but that one reader email is worth a whole lot of fancy dinners and double lattes. You will have to drag me away from this kicking and screaming. If readers are abandoning tech books, I'm not just going to sit by and complain. Maybe it means redefining the word "book," or redefining the word "tech," or even redefining the word "reader." And maybe there's nothing I really can do, but two years from now, I want to look back absolutely certain that I did not take it lying down.
Kathy Sierra has been a master Java trainer for Sun Microsystems, teaching Sun's instructors how to teach the latest Java technologies. She is also the founder of one of the largest java community websites in the world, javaranch.com.
Return to oreilly.com.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 13 of 13.
-
Cycles and Cycles and Cycles
2006-08-31 08:20:23 William B. Sanders [Reply | View]
-
Publish your article everywhere!
2005-03-23 08:20:19 Gizmo [Reply | View]
Kathy,
I will try to make my reply very short.
If it were my wish, I would just fill whole page with 'Thank you, Kathy and Bert!' phrase.
There are no words to express how much Head First Java book helped me in learning Java beginning concepts. I am still very new to it but with each page of this book I feel I know much more than I knew yesterday.
I wanted to write a big 'thank you' note to you, but have been compiling a very small list of things (feedback) about the read material. I am sure you got so many emails from readers with their feedbacks.
Today, I found your Manifesto and started reading it.
Your book made a huge impact on me, but your article made even greater impression.
Thank you for voicing your opinion and driving the nail into the problem.
Nail one: (your words)
[
"But what about computer programming? Security? Networking? Spreadsheets? Could we make some of the geekier and more traditionally work-oriented topics at least appear more like hobbies? Could we single-handedly reposition some of these technologies ourselves--to make people want to learn them? If people don't perceive the need, can we help create the need?
"
]
Thank you for that! I am one of the people who wants to learn new technologies (because they are new, in demand, and because I 'feel' they are going to be in demand when I read about them). But, I also sometimes want to 'learn', just to be on top of technology. When I pick up some books on some interesting subjects, I get literally 'turned off' -- why? -- too intimidating, too dry, too technical, too academic, too 'robot-like' a mindset. Unless you are a geek who wants to learn it and knows what to look for in that book, then many books on the market really cool off your appetite to ever read about this subject again.
Just go to ( I know you are a Java person, but for just my example, because I am currently programming in .Net) Microsoft site and really, really try to look at their articles and learn about their new technology...Too watery-like explanation, or too techinical explanation. I just want to ask after reading five pages of those explanations- "So what is it this wonderful thing you have been talking about ???!!!!"
Beleive me or not, your book not only helped me in understanding Java but also some parts of Java-mini-me-clone -- .Net technology.
Nail two: (your words)
["Maybe it's not even books at all that they want. Maybe they want to "learn differently," even if they can't articulate how that should happen"
]
True, very true. Thank you for noticing it and shovinig it in all our faces.
Ok, how about having Java tv shows?? Radio talk about recent technology trends? No, not recent hardware toys, we have it already (tech-tv like things). But really, a very down-to-earth tv shows meant for people who want to listen about latest technologies and maybe, more, learn something from people like you?
(Your words)
[
"...and I have pretty much zero talent for computer book writing..."
]
Wrong. You are a talent. Genius. Really. I think , a genius is not the one who comes up with something new, but who looks at something old , existing and says , - "hey , look at this, how about doing it this way?" People say : "Wow, Eureka!". No , not wow, it was in front of your eyes, you just did not see it this way, or deliver it this way.
(your words)
[
"
I am in the business of changing people's lives.
"
]
Yes, true. You are like a water in the desert of boring technical, geeky-oriented, life-absent books, failure books that plague the stores. You really give us the hope of wanting more and more from you.
If you write a book about cloning mice with rock from Mars and tell us there is life on Mars and it is populated with clones of mini-Michael Jackson, -- I will read it.
Again,
Thank you very much for being this soldier in a field and not willling to give up and producing such a wonderful piece of literature (yes, I dont read it as a technical book , but rather as a literature).
You are an inspirator
and please, please
don't
stop
writing!
P.S
Your opinion in your article MUST be heard everywhere, the book industry and those boring, damage-carrrying authors have to get a smack in the face before they really make a damage to people who want to learn.
-
Pay attention to fads
2004-12-17 13:35:10 davidleetodd [Reply | View]
Like the fashion industry, the software industry is driven by fads: "Hemlines will be shorter this year!"; "Service-oriented architectures will be hot this year!".
Software fads are largely propagated by industry analyst firms like Gartner and Forrester. Authors and publishers would do well to see what these folks are promoting, because you can bet that the software vendors will be following in a few months. It seems that book publishers focus on what developers wanted five years ago, rather on what the developers' bosses want today. There are hundreds of books on Java, but only a handful on Service Oriented Architectures. Yet SOA is what the bosses are ordering their developers to work in, and what the developers would buy books about if they could. -
Pay attention to fads
2004-12-29 05:51:53 jwenting [Reply | View]
writing to cover the latest fad is the last thing a self respecting author and publishing house should do as a core business.
Wrox tried that and it cost them their heads. Due to the extremely short timelines involved the quality of books went down, people lost their trust in the brand and stopped even buying the solid books Wrox also put out, and the entire house came tumbling down.
With fads lasting a few months at most the time is too short to write a book about them which hits the market up to date on the product when it is released and then gain enough sales to turn a profit before the fad ends.
Wrox countered that with their "beta books", books covering beta (or even alpha) versions of products and technologies in the hope those could then be updated to become the final book covering the final release version.
This approach has several problems:
Many such techs change considerably during that stage, causing largescale rewrites.
Customers feel cheated when their book about the beta product bears no resemblence to the final product.
And many customers probably expect some sort of upgrade path from the beta book to the (maybe never to be released) final version, something not offered.
Your comparison to fashion is valid in so far as magazines indeed can (and already do) pick up every latest fad and blow it way out of proportion as the best thing since sliced bread.
I doubt fashion books do the same. I'd venture that most will talk about more fundamental things like the best way to stitch a seam so it doesn't come loose rather than whether a skirt should be up to just below or just above the knee.
-
This could, and should, happen...
2004-12-17 09:23:47 kfarnham [Reply | View]
When a software developer looks at software development jobs in the United States, clearly it appears that there was a boom and now that has passed, never to return. It is true that most jobs have an historical duration. For example, the "career" of being a cowboy celebrated in movies lasted only for about 30 years, ending with the fencing in of the West. In that sense, we can say that the career of being the kind of programmer who prospered in the 1970s - 1990s has passed its peak for U.S. programmers. This type of programming is moving to India and other countries, where it can be done at lower cost.
The economic history of the United States is one of leadership in inventing new things. First we invent them, then we make the things for the entire world (providing many excellent jobs in the U.S.), then the cost of obtaining the means for making the things is reduced and other countries with lower business costs begin to make the things, and we import from them. People here who made those things lose their jobs, and the entire situation is very dismal, and causes real suffering to the unemployed individuals and their families.
However, this type of "creative destruction" has long been a hallmark of the U.S. economy, and is in fact the reason our quality of life is today so good.
To succeed, it is necessary always to be inventing the new, re-inventing new things that are like old things but in fact so much improved that after a few generations of reinvention you'd never guess where the original idea came from. Our U.S. economy has been very good at doing this. Despite the displacement and anquish that this causes, I'd much rather be here, a part of this vital, energetic economy, than live somewhere like France where they have 11% unemployment ALL the time, and you can get in trouble if the authorities see you working any extra hours above the mandated 35-hour work week (or whatever it is there at present).
In the U.S., our efforts can make a difference. There, everything and everyone is regulated. Here, creativity can be rewarded, and highly so.
With respect to technology: does anyone seriously believe it will cease to advance, cease to create new things. The NEW is where most jobs are created in our economy. How can Intel's multiplication of processing speed by 10 times between now and 2008 not produce opportunities for new types of software to be created for use on a home and business computers? Just as the stock market goes up, and up, and up, irrationally exhuberant, before it crashes down, then.. slowly.. recollects itself.. before.. proceeding again upward on the next wave of innovation -- so, software and the opportunities to develop and innovate within the realm of computers will have ups, downs, periods of creation of new opportunity, periods of destruction of over-extension and waste.
The world is changing. In 1900 everyone wanted the latest new thing, a "motor". Today, everyone wants/has a computer. In 2100, will people talk about "having a computer"? Do we talk today about having a motor? Yet, we have many of them, in all kinds of devices...
Computers are going to be integrated into society to the point where they will be invisible components that no one notices. The software that runs the computers will hopefully not also be invisible (I hope it's open source, that is) -- but software, code, will be like "law" (see Code and Other Laws of Cyberspace by Lawrence Lessig).
So, do we have nothing to write about? Ummm... I don't think we're in that situation. Must software books change? They will have to, since the integration of computers and "the Net" into society is changing, and changing very rapidly. Will there be jobs for software developers? Yes, when new companies start being created again (most new jobs are created in new companies, while old companies lay off people). Will new companies be created any time soon? It's starting to happen, again, slowly...
What's needed is venture capital. But venture capital becomes accessible only when the venture capitalist sees an exciting idea that seems very promising and pertinent. Where might these ideas first see the light of day? How about in the books we need to write?
-
Cost is an issue
2004-12-14 04:50:43 jwenting [Reply | View]
At the height of the boom there were so many books being released that the only thing that could sustain books WAS that very boom.
As the economy dropped like a stone people lost the money to buy all those books.
And a lot of that money hasn't returned now that people once again have jobs (or some of us do).
As to WANTING to learn, that's why I usually purchase books. My employers never paid a dime towards my training, I'm completely self-funded (which costs me about 10% of my disposable income).
But that means that as my income drops so does the money I've available to purchase new books. If book prices rise at the same time to make up for lost sales (publishers attempting to get the same revenue out of lower volume) I can buy even less.
Where in 2001 I'd purchase maybe 2-3 books a month in 2002 (when I lost my job) I purchased that many in the entire year simply because I couldn't afford any more (not having any disposable income apart from just enough to pay the rent and some food for half a year does that).
In 2003 I once again got a job but noticed that the number of titles interesting me had dropped to almost nothing. Lots of hyped tech as usual but I'd probably grown up enough to no longer be interested in that until it settles down a bit so I pass them by.
Now it's 2004 and I'm once again updating my library but more slowly (maybe 1-2 a month, down 50% from what it used to be).
I think many of your (potential) customers are in a very similar position to me.
They'd purchase books if they were interesting and have real value rather than just because they follow the latest hype.
So the market is indeed still there but many authors (as well as publishers) may be approaching it incorrectly if they think the customer still has the same attitudes and buying habbits (but at a lower level) than he did a few years ago.
-
Amen!
2004-12-13 12:40:38 Bill Siggelkow [Reply | View]
Kathy,
I haven't read Head First Java; but I would say that you are an excellent writer. If the tech publishing industry has writers such as yourself I am confident that we can survive and even excel.
I believe that the need for computer books has not gone away; in fact, there are so many new technologies based on open source that yearn for good books. I agree with you that focusing on fun is one good approach. I attended a tech session on Aspect-oriented programming; after the class my thoughts were "wow, this stuff is cool -- I want to learn about it!"
For geeks, I think that is what motivates them. I think another thing is that there are so many choices when it comes to software that no one has enough money to buy all the books they want. It's like we need a middle ground between the base documentation (usually just the API) available on the web and the focused writing found in a typical computer book. I mean I think it would be cool to have a book that showed me how to build a shopping cart web application in 4 different languages (e.g. perl, python, struts, .NET).
Personally, I do not think there is a replacement for the printed page; and I do not think that books will go out-of-style. I think the key is marketing (as you have pointed out). Again, I appreciate your thoughts and ideas; I hope that the powers that be (as well all of us aspiring writers) take your message to heart.
-
HeadFirst into the Desert!!!
2004-12-05 18:21:52 ryanbenedetti [Reply | View]
Kathy,
Your manifesto is just the kind of cold slap the tech publishing industry needs! Bravo for calling out the hardcores and leaving the soft-spined behind.
I consider the HeadFirst series to be classics not only in the field of IT publishing, but in the History of Pedagogy and in the History of Human Ideas. I will be using HeadFirst Java in my Programming 1 course next year.
I hope other authors take your manifesto to heart and follow your challenge. I am afraid, though, that the problem is this: the brain trust in the IT world is dwindling in number. I don't know why we suddenly face this desert of genius, but it surrounds us. If not for you and Bert and the thinkTank at O'Reilly press, we everyday geeks would be left extremely thirsty and extremely lonely.
I thank you from the bottom of my soul. HeadFirst has not only validated my tweaky sense of humor but also my learning style. Finding your books has been like finding a true home.
Sincerely,
Rhino Benedetti
-
What Kathy Doesn't Say
2004-12-05 06:16:44 Tim O'Reilly [Reply | View]
Because she's so user-focused, Kathy didn't toot her own horn! So I should do it for her. Her first book for O'Reilly, Head First Java, immediately vaulted to the top of the Java charts, where it stayed for the better part of two years, achieving sales numbers that would have made the book a bestseller even during the boom years. What knocked it off the #1 spot in Java? Head First Servlets and JSP, her latest book. Meanwhile, a book whose development she conceived and supervised, Head First Design Patterns, by Eric and Elizabeth Freeman, just replayed the same pattern of going to the head of the list in another coveted publishing category.
Kathy and her husband and writing partner Bert Bates aren't just spouting hot air. They are demonstrating that the philosophy espoused in this piece actually works. Kathy, you're an inspiration!
-
Hurray fun books!
2004-12-04 21:35:18 scottwalters1 [Reply | View]
Absolutely! Well spoken!
I'm going to reply in the form of an anecdote but only because I suspect my habits mirror a lot of the ORA book-buying population.
In the average day, I don't pick up a book, though I have lots I could pick up. Most of them are on topics I already know something about: Perl, Java, Linux, network security, etc. I don't often buy or read books to learn something new unless I know I'm going to have to thorougly learn that skill - but most of I have to do dumb little chores - figure out how LILO works (I'm a NetBSD guy normally); figure out how to install Slackware without the luxory of a CD-ROM (hint: Zipslack then use that as the installer); write a grammar for a format I didn't previous know; learn a little Processing and a little Squeak to share the joy; ... that's been my past few weeks. When I hit a whole in my knowledge, books don't serve well. Books are too big, too broadly focused, too expensive, not readily available, and are only printed on cash-cow topics I don't care about or already know enough about.
I hear you suggesting more books, smaller books, on more topics, on topics that Borders (screw 'em) wouldn't even consider stocking (until after they become popular), and more tightly focused (perhaps "Squeak Essentials" rather than "Learning Smalltalk and Graphics Programming oh and by the way we use Squeak"). Well, hello! That's what I want! Praise be!
The suggestion of including "fun" touches on something more profound: books now try to impart knowledge, but they rope the reader off by every plastic chain, picket fence, and moral dictate ever erected in the field. This leaves the reader with an accurate view of the most common cases how the technology has been used in the past but is worthless in giving the reader a view on the interesting uses or potential future uses. These books are obsolete before they're conceived. Case in point: I like where some of the "Hacks" books are going, but the "hacks" are, well, recipies... these things are essentials, or old stand bys... they aren't hacks. A more fun-oriented book that didn't care about its shelf life would explain how to crank the power up to a full watt on common gear; it would show exactly where to put the pig tails on; it'd give the gain ratings for various industrial and commercial antennas such as the 30-footers that set that DEFCON record. Those aren't hacks either, exactly, but we're getting there. It'd list retailers that sell serial-802.11 adapters (these exist) and show how to hook up 802.11 to a BASIC Stamp processor (if you can't wire something up to an embedded controller, you can't hack). It should talk about scripting action so you can walk or drive around with an 802.11 enabled machine and have it perform actions. I'd like to see a discussion of auto-aimers - something the boring grampas with DirecTV have on their RVs. In short, I'd like a book talk about everything that people aren't doing with the technology - at least the boring people.
Right now, as a geek, books on other topics besides the topics I know aren't interesting because they suck the life out of the subject by this kind of pandering-to-the-norm that's exactly what sells a book to a publisher ("my experience shows that exactly half the population knows how to tie their shoes and the other half wants to know how!"... "Great! Let's make a book!"). Someone set up VoIP at Burning Man with a pay phone (real in every way except for the 802.11 link to a sat uplink). After reading a book on 802.11 I should be two steps away from that same idea - I shouldn't suddenly feel like I'm not way overqualified to set up WEP and download crap.
For what little its worth, I've tried to sell off-the-beaten-path ideas to publishers and I've seen them lose interest every time. I've had counter offers that sucked the life out of the idea, and I've proposed counter-counter offers. One of these is due in stores soon - but thinking back to the proposal process, I think I've tricked the publisher, Apress, into printing something bizarre - I've written a book on doing things that approximately zero people are doing right now. May I be your case study?
-scott?
-
I want...
2004-12-02 05:18:44 Bluey [Reply | View]
I would love to see programming books that document real-world development, step-by-step.
For example, a personal project of mine is an industrial-strength CMS. I have been developing this software for four years, continually adding features, optimising code, refactoring, etc.
During the course of the last four years, I have learned mostly through trial and error and judicious Googling. Of course, I've also had my favourite O'Reilly books close to hand for reference.
I could have saved three years if I'd had a book that documented the development of a commercial-grade CMS. If I'd known, before I started coding, that I'd have to address issues like scalability, fault-tolerance, redundancy, caching, session management, versioning, user-interface design, templating... then I could have been better prepared for the project in hand. I wouldn't have made some of the mistakes I made (I appreciate that I would have made an entirely different range of mistakes).
Why can't authors produce more real-world books instead of more "Hello World!" books? -
I want...
2004-12-04 21:50:27 scottwalters1 [Reply | View]
Ahhh, but authors are writing "real world" books. To use Java in the work place, you need more than anything an API reference set, and that's exactly what most Java books are. To use Perl, you need to know about the core modules, style, idiom, and utilities surrounding the language - that's exactly what's documented in ORA books. A book isn't going to print out a 100,000 line listing of a major project - you can find plenty of those on the 'net - but a book like Perl Medic will give you specific methods for unraveling them, adding tests to them, and refactoring them (or gutting them). It doesn't get any more real world than walking into a 100,000 line project that needs tests written and refactorings applied. These books need to be - they shouldn't be pulled from the market. However, we need a new kind of book. What would be in a Perl Hacks book? Let's see... a toy network scanner; sending broken packets using SOCK_RAW; cross compiling perl and building it static to load it a Gumstix board; using Perl for robotics control(see previous point); using SDL and Perl to draw pixels in a frame buffer or window; scripting other processes in OSX, Win32, and Linux (X can be scripted - and I really wish I knew how - but no one is cool enough to write a book on it!); implementing a user-mode filesystem on Linux with Perl; ... a thousand other things. Again, these are exactly the things that people don't normally do with Perl, don't get jobs using Perl for, but would enjoy using Perl for. I'm singling Perl out for this purposes of this example but the philosophy applies equally everywhere.
-scott



Thanks for your comments. My experiences writing computer books go back to the first wave--back in the 1980s. Everyone was buying their first computer--mine was an Apple II+ and after a while I got a disk drive and didn't have to use my tape recorder to record my programs but could save them on a big 140k floppy. Learning AppleSoft Basic or any kind of BASIC was a pain because the only computer books available back then were generic Basic. This was before Amazon.com, and I remember thinking that I could do a better job than the generic Basic books and wrote a book on AppleSoft that took off 100,000 copies right off the bat. Then I did it again with the first Commodore 64 book 350,000 copies. Then the bottom fell out (for the first time.)
However, it came back again with HyperCard, and with my first earnings from my HyperCard book, I went and bought an airplane. Then it went away again.
However, like the proverbial pendulum it came back like gangbusters with Java (as you noted) and everything Internet. I missed that altogether, but with an early Flash book which was right around the bubble burst, things were good again.
My own opinion is that books like the Head First series represent their own revolution. Smart books, innovatively crafted will always be important.
Kindest regards,
Bill Sanders