Lessons learned: radio interview

Ok – here’s my notes from my first radio interview experience. I was on air for about 15 minutes on the 5/22/2005 Business of Success radio show.

    1. Calm down. If you listen carefully to people that speak well on air, they speak slooowly. They hit all the syllables. And more importantly, they sound calm or in control. My first 10 minutes were not calm, and I didn’t sound particularly in control. I smoothed out later on, but had the interview only been 5 minutes… I thought I’d be fine here since I’m a good public speaker and have tons of experience. The difference here was control: I wasn’t the host, I was the guest. I didn’t have my hand on the throttle, Alan did.
    2. Practice. Whenever friends have job interviews, I always offer to do a practice interview with them. Well, my wife offered to do a practice radio interview with me, which I declined. With a “I don’t need that kind of help” shrug. Well, in retrospect, it would have helped a ton. It would have forced me to run through things and recognize mistakes or bad habits. Since I didn’t do this, the live interview now serves as the place I learned from.
    3. Know the 3 things you want to say. The questions I got were open enough that I had lots of room to decide how to respond. If I were smarter, I would have related things back to the book, or back to the 3 or 5 key things I wanted to try and say. I’d have been ready to say 5 second, 30 second and 1 minute versions of those key things. I’m not suggesting spinning or manipulating questions: only that in this case there was plenty of room to answer questions and hit key things I wanted to hit. (This would have been a good thing to practice).
    4. Listen to other interviews. I listened to 3 or 4 other interviews from the same show just to get a feel for Alan Rothman (the show’s host) and take notes on how other people handled the interview. Especially if you do a practice run, it’s easy to catch good and bad things in other interviews.
    5. Know the format and how much time you have. I was lucky to have a 15 minute slot all to myself. It’s typical to get shorter slots, or be part of panel or talk show on some other specific topic. Either way, make sure you know exactly how much time you will have, whether you’re sharing the time with others, who is interviewing you, and what the focus of the interview will be. Use this to help practice.
    6. It goes by very fast. I expected this but still felt it all went by very quickly. This is another reason to practice – to help it seem familiar and slower. The commercial breaks, as annoying to listeners as they are, were great for me. It gave me a chance to calm down, consider what I’d said, and what adjustments I needed to make. Make sure you know how many commercial breaks there will be and how long they are.
    7. You are on your own. One surprising thing in being interviewed was how little guidance there is. Alan was kind enough to chat with me the day before which helped me know what to expect. But the day of had no prep at all: you call in a few minutes before you go on, then you hear him announce your name, and then before you know it, it’s all over.
    8. Consider what you are representing. Many of the better interviews I listened to were focused on one of 3 things: a company/service, a product (e.g. book), a person (CEO of JetBlue, rock star, etc.). Some people who were on because of their book spent more time talking about their company/service. Others went the other way. I think next time I need to be clearer on what the audience value proposition is: the book? me as a consultant? me as a person and my experiences? A combination of these things? Why are they not going to turn the dial? And within the things they’re interested in, what i can say that serves my own interests as well? I don’t have answers to these questions, but they’ll be what I’m thinking about before the next interview.
    9. You are on your own. One surprising thing in being interviewed was how little guidance there is. Alan was kind enough to chat with me the day before which helped me know what to expect. But the day of had no prep at all: you call in a few minutes before you go on, then you here him announce your name, and then before you know it, it’s all over.
    10. Ignore host responsibility. This is a minor one, but 2/3rds in I stop myself short because I heard the commercial cue music. Big Mistake. First, you can talk over the cue for a few seconds. Second, it’s not my job. The host will interupt when it’s time – because I cut myself off there’s a good 2 seconds of dead air for no reason. Let the host manage the show and you – keep going.
    11. Relax. . Even though all the other bullets are super analytical, none of the analysis matters if I’m not relaxed enough to make use of it. Personality counts, and I probably can’t be me if I’m doing interview calculus in my head while trying to carry a conversation. So practice a few times, consider the above list, but on the day just let what happens happens and try to have fun.
    12. No ums, or other bad speaking habits. This comes straight from any guide to public speaking. Watch out for bad habits you use when speaking under pressure. Common ones are: using um, like, or well, between words. Repeating the same introduction or endings to sentences such as “In other words” or “.. of that nature.” Sluring, slang, absences of any pauses are other common bad habits. The only way to get rid of them is practice.

If you listened in and had any comments or advice for me, feel free to leave it here.

Radio interview link fixed

The previous post had it wrong: here’s the correct link for the radio interview. Jump to 27:30 if you want to skip the first guest.

For those keeping score, I give myself a C (a passing grade) on this interview. Watch for “radio interview lessons learned” in an upcoming post. Made some obvious rookie mistakes, despite trying to avoid them :)

Thanks Faisal for catching this.

First review: 43 folders

Here’s the first online book review I’ve found, from 43 folders’s Merlin Mann:.

Where so many Project Management books fetishize GANTT charts, waterfalls, and abstract planning methods, most of Berkun’s book lives much further down in the trenches—where misunderstandings happen, dates slip, and bad decisions threaten to derail your project. The book is full of really practical advice on handling these challenges in the real world. And, yes, I really wish it had existed 7 or 8 years ago.

Full review here

Radio Interview: sunday

The business of sucess radio program is interviewing me on Sunday to talk about the book – They’re syndicated nationwide. I’ve been on TV once before in 1997 (don’t try to find the footage – its been happily destroyed) – but this is my first radio thing.

I’m the second guest on this archive recording of the 5/22 show (mp3)
(jump ahead to 27:35 if you want to skip the first guest, Joe Vitale author of “The Attractor factor“)

Book tour: lessons learned

Here’s my notes from my first book tour (one city, 3 days, 6 appearances). Here’s your chance to learn from my mistakes:

  1. You will be overwhelmed. There are too many logistics to juggle at the same time with too many different people not to screw things up. It’s ok, it’s fine, but prepare to leave things, forget things, and make mistakes. As Durden said, if you want to make an omelet, you have to breaks some eggs.
  2. Make a daily itinerary. I had a daily itinerary set up with address, directions, and contact info. Before you go to bed, make sure everything is set and confirmed for the next day. Margins of error are small, and people expect you to arrive at certain times.
  3. Don’t trust technology or anything else. Things always break. Murphy’s law is alive and well in 2005. Expect presentations not to work and video equipment to fail. Transportation will be late. Compatibility is a myth. Be ready to talk about the book without any technological support, even if just for 10 minutes – that’s enough to give people some context and ask you questions.
  4. Get everyone’s business card. I have a decent memory for faces, an excellent memory of ideas, but a horrible memory of names. I didn’t get nearly enough business cards from people. I love questions and thinking about them, but there’s never enough time. E-mail is better. And I know the routine, grab card, write note/comment/question on back, put in secret special non-forgettable place in clothing, review later. But I was overwhelmed (see #1) and unable to remember to do this nearly enough. I’d have asked people to do this, hand me a card with their question on it, but historically this never works – people won’t do it. The whole business card thing is awkward, but I’ll just have to suck it up next time.
  5. Be friendly and open. This is basic presenting advice, but I’m there to invite people to spend more time with my book. If I can’t do that in person, I don’t blame people for not placing much hope in the book. I tried to think of myself as a host for the book, and the talk was the tasty appetizer. If I seem smart, and the appetizer good, they should want, all on their own, to buy the book. Smart good books are rare.
  6. Two talks a day is enough – The most valuable, interesting part of the whole experience was talking to people before and after the actual talk/seminar thing. That’s when there’s some shared context and the chance to get to know people. If you do more than two talks a day you will running from venue to venue, and not get much interactive time with people. If you don’t want that, fine – go for 3 or 4. But if you do want to go deeper into people’s questions or learn something, 2 seems about the maximum
  7. Have free things. Free books helped get people to stay for Q&A. The flyers and postcards I had gave people something to take with them if they didn’t get a book. In a pinch business cards can work, but I think ideal would have been a sample 4 or 5 pages from the book itself.
  8. Rest your voice. If you go 2 or 3 lectures a day, plan quiet time. Drink lots of tea. Last thing you want is to lose your voice before your last few dates. You can go out, but warn people you won’t be talking much.
  9. Plan a social event. As a total no frills impromptu thing I invited everyone I met out for drinks at a pub. Was fun. About 15 people showed in the course of a few hours. Most didn’t stay long (and a few grabbed a book a left), but the whole experience was positive. Unlike the run and gun lecture experience, at the pub everyone is chatting and the environment is social. If you’re not as attracted to risk as I am, you could get confirmations from a small nugget of people to insure against drinking alone.
  10. Everyone matters. Crowds are over-rated. No matter who is there or how many people show, your performance should be the same. The smaller the group, the bigger a slice of your energy you can give to everyone that’s there. I’ve presented to 1000 people (umm, not on this tour) and 10, and sometimes I think my time was better spent with the 10. Don’t worry about numbers – worry about who’s in front of you, and how effective what you’re saying is interesting to them.
  11. Gigs are network dependent. I spoke at places where my network reached. I asked friends, acquaintances, people I interviewed once, old managers, websites I’ve read, you name it. I sent mail to baychi and other professional groups, and just asked around until I found enough gigs to fill 3 days. I was told NO many times, and didn’t get responses at all from various places. Hiring a PR person might help, but I didn’t have one. See the previous bullet – if you can only find 3 gigs of 10 people, that’s 30 people who will know of you and your book that won’t if you don’t do a tour. And in theory a great way to grow your network is speaking – hopefully for my next book, it will be a little easier to find places to speak.
  12. Consider tag-teaming the tour. Given 1,2 & 3 there are good reasons to have a supporting person around to help/share with various kind of logistics. I imagined at a certain moments how much easier and more fun the whole experience would be if I was sharing it with another author (or had a friend willing to be a roadie for a few days). The costs might be lower or the same, but the logistics would be much easier, the social would draw more people, etc. Not sure it would work, but it was a thought I had several times.
  13. Remember Walt Whitman. The man known as one of America’s greatest writers used to go door to door selling his poems. Yes door to door. Imagine: knock, knock. Door opens. “Who’s there?”. There stands a strange poor looking man, in ragged wrinkled dirty clothes, with a big white beard and crazy eyes. “Hi, I’m Walt. I’m a poet. Can I…”. Door slams shut. Repeat. If Walt could do poetry door to door, it’s within your talent and pride to tour and talk about whatever it is you’re writing about.

But the big question is: does this help sales at all? I have no idea. I have to say yes, in that I’m an unknown and this got me (positive) exposure to about 300 people in 3 days. So I’d say this gets the book on the playing field with people – whether they buy it or not is based on so many factors that I have no control over it’s not even funny. But a book tour is one tool I have, so I used it.

Total score:

Cost: $800 (plane ticket, 3 nights lodging, rental car)
Time: 3 days
Gigs: 6 (3 different lectures, which paid off as I saw some people twice. Hope they were impressed :)
Total attendence: ~350 (Google: 100, Baychi: 100, Sun: 30,Adobe: 40, Yahoo: 40, Macromedia: 40)
Fun had: much
Pints of beer: many
Books given away: 70 (Thanks to O’Reilly)
Power cables lost: 1
Roadside assistance calls: 1
Bad meals: 2
Forgetable meals: umm
Good meals: 2
Moments of extreme existential angst: Once per day
Moments where I felt like a vacumn cleaner salesman: Once a talk
Desire to write more books, despite all this hard work and unclear returns: High

Last stop: Adobe

On Thursday May 12th I Left Macromedia at 1:35pm. Just enough time to make back down to San Jose by 3pm.

I’d been to Adobe once before – when they were in their old offices back in 1994. I interviewed for a software engineer job that I didn’t get. But I still have the nice black and red adobe mug they gave me, my sole prize for the two days of interviews I had.

Adobe's two towersAnyway – Adobe is headquartered in two towers (hmmm) on Park Avenue, San Jose. When I saw them, and the adobe logo on top of the 20th floor, I sad “wow”. By far the biggest most archiectually dominant building I’d seen on the tour.

Katja, my most excellent host, met me downstairs and we headed up to the conference room. Highlight of the walk up was the gorgeous basketball court on a large patio between the towers. Awesome (although it seemed like a windtunnel – not a place for an afternoon picnic – long range gamers would suffer).

At the talk: spoke to a mid-sized group of 30 or 40 people. Met Tarjin, a usability engineer I knew back at Microsoft, who’s now at Adobe. By 3:05pm we were underway. The group was fun – most receptive to jokes on the whole tour (or maybe my jokes were better? who knows). Talked about schedules and teams, and how to make things go well on a timeline. Got a few questions about design process and managing ideas on a timeline, and I pulled out some diagrams from Chapter 6.

I said goodbye to the adobe folks, and finally headed back to my hotel and my first dip in the swimming pool that’d been teasing me throughout the book tour.

Thanks to everyone that came out to see me – check out the book and let me know what you think.

Day 3: Macromedia & Automobiles

Made two mistakes: 1) left power cable at Google. 2) Left lights on rental car.

The loss of the power cable made every talk a Mission impossible type adventure – certainly helped prevent me from lingering self indulgently on slides (it’d be fun to make this a rule at conferences – take too long, your laptop shuts down automatically).

The dead battery in the rental car at least stopped me from worrying about the power cable.

Macromedia, SFI had thought I’d get up early Thursday morning, stop by Google and retrieve the cable, but the lack of anything resembling power in the battery of my car made this impossible. Tip: the extra money for hertz is worth it. They had a service person there to give me a jump in about 45 minutes (btw: the Sheraton folks refused to help – “against policy”. To jumpstart a car? They have a policy for that?)

I managed to get to Macromedia, on Townsend st. in San Francisco early – walked around. Odd neighborhood – semi-industrial, but with mostly high end designer furniture and home decoration stores. The one lunch spot I found didn’t open till 11am, so I went for a walk around. The Macromedia building stands out on the street – it’s a beautiful brick building with steel awning over the front stairs.

Inside I used their self-service visitor terminal to create an id, including a photo (taken from said terminal). This was the coolest id creation thingy I’d see on the whole tour. Everyone, except Sun, had systems like this one, but the whole self-photo thing was unique to Macromedia.Badge from automated visitor terminal

I was in a small room near the lobby – but we filled it. About 30 or 35 people, mostly program managers, with some documentation, engineering and design/usability folks. The group was great – lively, asked lots of questions, and made the session more interactive than average. During Q&A. which went for a good 25 minutes, someone asked the perenial PM question “Is your sock drawer organized by color?”, To which, after faking offense at the question, I answered “I don’t have a sock drawer”, and left it at that. How mysterious.

After grabbing a cookie from the pile of foodstuffs for the talk at the back of the room, I thanked Cecilia, my host, for having me, and headed off down to San Jose, for Adobe – my last stop on the tour.

Day 2: Social event: Faultline brewery

Just for fun, purely for the sake of experiment, I invited everyone I spoke with out to drinks at a nearby pub. Folks I knew were around, Matt, Chad, and some others, I asked personally, but for the rest – I left it to chance. At each gig I’d announce early that anyone interested in the book, in me, or some free beer, should head on down. The big question was who would show? Anyone? I prepared myself for drinking alone (not difficult for most writerly minded individuals). And besides, there was NBA playoffs to watch, and I could always annoy the bartenders by showing them my book every 10 seconds.

Faultline brewery, SunnyvaleAbout 12 people showed over the course of a few hours. Given I’d never met most of these people before, I was pleased. None of them tried to sell me Amway goods or convince me that the end was near. The conversation and beer was good. I’d definitely do something like this again next time.

Day 2: speaking at Yahoo (Wed may 11th)

The comfy chair at yahooI arrived at Yahoo’s building D at 3:30 – right on time for my 4pm talk. Everything inside was wonderfully purple and yellow, including the big oversized comfy recliner in the waiting area. I explored the Yahoo store in the lobby, looking for a pair of purple and yellow boxers, while waiting for my host Bob Baxley, to arrive. I knew Bob from helping with his fine book on web applications, but this is the first time I’d meet him in person.

I spoke in a small room to about 25 or 30 project managers, designers and other folks. Met Chris (?), someone who worked in Microsoft’s Mac group, and knew me from back in the day. Always fun to meet people – never know how you know someone. Always funny to throw names and see which ones jog a memory and which ones get blank stares.

I did the schedules and lies talk, and it went fine. Finished in about an hour with another 30 minutes or so for questions. The rule of thumb: if folks stay for Q&A, you did ok. Well, most of the folks stayed (The offer of free books helps I suppose).

Book tour score: 4 talks down, 2 to go. One box of books left.

Day 2: Speaking at Google

Stayed up late tuesday night working on slides for a half day at google . During the baychi talk, believe it or not, I came up with some changes I wanted to make. Didn’t get home from baychi till about 10:20pm, but was in bed before 1am.

Woke up early enough to get some exercise – I can be super cool presenter dude only if I get plenty of exercise. If I don’t exercise, the whole process of being a speaker isn’t as much fun – but If I exercise, I’m a buddhist monk (as in mellow and smiling deeply) through the whole process.

Scheduled to go on at google at 11am – Arrive early. Way early. 10:15am early. Drove around the outside of campus to see what else was in the neighborhood. I thought the campus looked familiar though I’ve never visited google before… then I saw that tall outdoor sculpture of a man – and realized it was the old Sgi campus!

Google campusGoogle campus has the vibe you’d expect – young, smart, and well financed. The architecture is fun. If you believe in the effect environment has on psychology, you’ll love this place. It’s stimulating and open- toys, games, volleyball court – it’s obvious the place is meant to be feel like an adult playground. And inside the buildings is much the same – big spaces, interesting shapes, open workspaces – little of the reptition and monotony found in most office buildings. (At first it reminded me of the blender, a Dr. Seus style incarnation of building A on Microsoft’s redwest campus that was remodeled into a conventional space years ago).

The talk was in a big open room in Building 43 – it felt like being inside a big piece of swiss cheese: the room was nearly triangular, with big holes leading out into other areas. The room has no doors – just two big wide slots for people to enter and leave – I’m pretty sure this was not the room they used to have their top secret uber-private conversations.

Carolyn Yates, my host, was great and showed me around, and got me set up. The tech folks were there and got me set up in 2 minutes. At 11:05, we got started. Had about 100 people there – and more showed up after we started. I remember there being a row of folks standing towards the back.

The talk was a special one – I didn’t do it elsewhere on the tour – it was about stuff I learned while working on web browsers during the first browser war. I talked about managing team size, process and specs not being evil, and the tradeoffs of business, engineering and customers. I think it fit with the issues I guessed Google was dealing with, and the audience responded well. They laughed at jokes, paid attention, and a good crowd stuck around for Q&A. Many of the questions were about Firefox, browser design and strategy, but about half were about project management and development. I should have mentioned that Adam Bosworth, currently a VP at google, was a key player in the early parts of the browser effort – they have a expert on many of these issues in their midsts.

In the afternoon I did a second section with a smaller group of project managers – the safe bet would have been to work from a set presentation, but I went informal – it was only 20 people – and I tried to build up something from questions. I’ve done this dozens of times and its usually more fun for everyone. But this session did not go well – they weren’t happy with it and I wasn’t either. The feedback I got was that more examples from my own experience would have been better – but I was afraid to focus on that as a former Microsoftie speaking on google turf – I thought it’d all be rejected if everything I said came from my war stories. So instead most of the conversation was flat, and never got into good back and forth riffs. ( If you were there, let me know what you thought – I can probably learn something). One question I should have asked, but didn’t, was whether these folks worked together or not – informal/dynamic sessions run much better if it’s an intact team, vs people in the same role in different parts of a organization.

I met several other google folks, and they were all great – asked good questions, were friendly and generous to me – But I didn’t catch nearly enough names, or business cards – a mistake I made many times on this first time solo author tour. If we met and talked, drop me a line.

I left google around 1:30pm – Just enough to time to head back to the hotel for a quick shower and something else to eat, and then off to Yahoo!

Day 1 continued – baychi

Speaking at baychi is one of the best speaking gigs – they take you out to a friendly dinner, they give you a t-shirt, and everyone you meet who volunteers is friendly, funny and cool to work with. I spoke at baychi once before, back in 2002 (thanks to Richard Anderson) and had a great time, and was looking forward to coming back.

I did a different lecture at baychi – Sun’s talk was about schedules and lies, baychi was about projects that go wrong. Had a good crowd – I’m guessing about 100 people. Somehow in my memory, the pARC auditorium was larger, more like one of the old Microsoft lecture rooms – but I’m glad it was the size it was, since it felt full (Nothing worse than being in a stadium sized hall that’s filled with 3 people: you, the janitor, and your host).

Speaker parking, @ Baychi (PARC auditorium)I gave out about 15 books to folks that asked questions – which i learned was the smart way to use the promotional copies I had (a tip for any future book tour planners out there) – it got people to stay, and it got them to participate, and gave the vibe of everyone being interested in what I had to say.

As it turns out, the Q&A part is the most fun part of the whole thing for me – I know my material.. I know my slides, so it’s only so interesting to me (Especially on a tour where I get to hear myself do the same thing again, and again and again – how do rock bands do this?). But questions force me to really work and communicate, and it’s the most enjoyable and challenging part of the whole experience. If I could do shorter talks with longer Q&A sessions, I would, but few audience these days have the attention spans to sit through long Q&A sessions.

I thought it was interesting how social and human the questions were – lots of thoughts on power, working with people who don’t see disasters happening and how to deal with them, comparisons to the film industry and how it deals with similiar problems (Hi Ari), and other questions about situations folks were in. The Q&A period was fun – I don’t remember that many of the specifics, I was up there for close to two hours, but I do remember a lot of laughing, and feeling good, both in me and from the crowd. A good experience all around.

Book Tour Day 1 report

Day 1 – Tuesday, May 10th. Started not as expected – tripped getting out of the shower, dodged the toilet, but jammed my toe during the tortured dance that was required to regain my balance. Fortunately I did manage to avoid tripping over my towel and falling flat on the tile floor. Book tours are supposed to end on naked the floor- not start that way.

The non-bathroom/naked part of the day started with a trip to Sun Microsystems – The Newark campus is up north and across the bay, but staying in Sunnyvale it only took 20 minutes to get there. I arrived early and Met Aimee – the host of the series i was speaking at. She was great (though initially, and understandably, tired from lugging the 50lb box of books O’reilly had sent from her car). While waiting for Aimee at the front desk in building 16, the woman at the desk confirmed that i was, in fact, in the quietest lobby she’d ever been in. It was almost relaxing being there (minus the latent fears i had as a former Microsoft employee entering Sun Microsystem turf). I signed the usual visitor/NDA forms, got a badge, and followed Aimee inside.

Sun Microsystems, Newark CampusAt the talk we had about 40 people show up, plus another 15 or more on conference call.

Pros: Good, smart crowd. Good questions, and no one fell asleep or threw anything (two hallmarks of decent presentations). They laughed at some of my jokes. Cons: 25 minute struggle with a projector, which included an inquisition about my laptop, ane it’s inability to produce proper video – but I was vindicated, as a replacement projector worked fine. Gave away half the box of books, saving the rest for lecture #2, the biggest (or so I thought) of the tour – baychi, later in the day. One of the good questions I got included a good pointer for a book I should check out about a biography of Cray (the supercomputer dude) and the way he organized teams.

The start of rank checking..

I’m well aware of how misleading these kinds of rankings are, but apparently the book is currently listed on amazon as:

#771 in Books
#19 in Computers and Internet

I know, I know, I know.. wait 20 minutes and those numbers will double. It’s like the guy who sprints out to take the lead in the first 5 seconds of the NYC marathon, he waves to the camera, and then you never see him again. I’m that guy. But while I’m somewhere out front, I’m smiling :)

How you can help me

Ok. I need your help. I’m a first time, relatively unknown, author. Getting a book published is a minor miracle in itself. But about 50,000 books get published every year, and very few of them stay on the shelves for long. If you’re interested in me, the book, or the future books you imagine me writing, I need a favor – I need your help to make the book sucessful.

Here’s what you can do:

  1. Buy the book.
  2. Write a review of the book on amazon, or your own blog/website.
  3. Talk to other people about the book and show it to them. Show ’em the blurbs and sample chapter.
  4. Know any college professors? Professional group leaders? Managers? These are all folks that might be interested in a good book to give to their teams/students/groups.
  5. Go to your local bookstores and ask if they have the book. Simply asking about it, even if you don’t buy it, draws it additional attention from booksellers. It helps.
  6. Know someone that works at a public radio station? writes a business or technology column for a paper or magazine? Or a event/conference that needs a public speaker? I’m glad to be interviewed or talk about topics from the book.
  7. Post some questions or comments in one of my forums or join the pm-clinic.
  8. Thanks for your support – I can use all the help I can get.

Tour dates

Here are the final tour dates for SF

Now thru May 20th

Tue, May 10th

  • 11am, sun Microsystems (newark campus), talk: schedules and other lies
  • 7pm Baychi, talk: What to do when things go wrong. Open to the public.

Wed, May 11th

  • 11am & 1pm, Google, Mountain View, talk: lessons from the browser wars
  • 4pm, Yahoo, talk: Schedules and other lies
  • 6pm7PM, Faultline Brewing Company – Purely an informal social thing. Share drinks and food with this new author. I’ll have a bunch of free copies of the book to give away. All are welcome to come and chat over some beer. Talk about the book or anything you like. I’ll sign books or other things if you desire.

Thur, May 12th

  • 12pm, Macromedia
  • 3pm. Adobe

If you’re interested in the Wednesday meetup, leave a comment so I’ll look for ya :)

Mysteries of book publishing, part 1

The transport of books from the publisher, to actual stores, is something of a mystery. It’s supposed to take 10-15 days for books to leave the publisher, make it to distributors, and to stores. But since these things move of trucks, in big skids, and spend time in various warehouses, or waiting to be stocked on shelves, there’s no specific dates for these things. Just ranges of time.

Today i dropped by the local Borders and asked about my book. They told me it wasn’t in yet, but they didn’t know why, since it’s official publication date was 4/25/2005. They said they’d ordered 20 copies, and she told me where they’d be shelved. Beyond that, she had no idea.

So here’s a favor I’m asking: if you don’t see the book, ask. The more folks that ask about the book, the more likely they’ll order some if they weren’t planning on it. The more folks that ask about a book and buy it, the more likely it is they’ll stock it, or put it somewhere others might find it.