I don't see my book listed there. https://www.oreilly.com/library/view/tragic-design/978149192...

Is this specific to programming topics?

I can't speak to best practices, but I can to worst. Tragic Design [0] is a text I've recommend to others in the past. It's important to not just know what to do, but also what not to do and why. I haven't reread it since it came out of beta, I read it a few months before it was published and found it to be good. It gave a lot of examples of poor design decisions with physical systems and analyses of how they led to accidents (or near accidents).

Two examples that have stuck with me:

Descent angle/rate shown and entered on the same display, the mode determined whether you were entering an angle in degrees or a rate of change in altitude. The difference in display, aside from the mode indicator (a single light) was a comma (rate) or decimal (angle). Entering an incorrect value because the pilot thought it was in a different mode resulted in a much faster descent and accident. Imagine this on a simple LED display (but smaller than your standard alarm clock):

  .   1,000       1.000 

And it's not the only control or display in view and those two numbers mean very different things.

Another was a control for a ferry boat with two engines. Depending on which engine, the control for engine speed could mean different things depending on which engine was the active engine. Visual aid:

    |========|    X          X    1          2 

If engine 1 is active, pushing the speed control away may mean go to the right, if engine 2 is active it means go to the left. The indicator to know which engine was active (as I recall) was the same uniform sized small indicator used for every system status indicator. Forgetting that they had switched engines (to "pull" the ferry to its destination versus "push", due to damage or other issue with the desired engine) the operator accelerated rather than decelerated at the destination.

[0] https://www.oreilly.com/library/view/tragic-design/978149192...

I've been writing a book on ways design can play a critical role in our lives. This reminds me of one of the stories in the book: A pilot cashes a plane because he didn't realize which decent mode he was in and 3.3 and 33 look awfully similar in the display. These things can be the difference between life and death.

For those interested in more: http://shop.oreilly.com/product/0636920038887.do

I'm currently an author with O'Reilly, writing about the design space. (http://shop.oreilly.com/product/0636920038887.do)

I am in the final stages after over a year and half. I was in your position not too long ago and researched as much as I could before accepting, so I will skip things you will find in a quick Google search.

Negotiating:

1. Everything is negotiable, remember that

2. Under promise on #pages, they ask you for an estimate but lowball it because thats how they price it and then will ask you to fill it.

3. Get in writing what they will be contributing.

Choosing the topic:

1. Choose a topic you are passionate about

2. Choose a topic you know a lot about

3. Choose a topic you can write a lot about

4. Don't be afraid to tweak the topic half way in.

5. Choose a topic that will sell in a year and half.

Writing the book:

1. Write an outline, write the first chapter, throw it away, and rewrite the outline agin.

2. Its better to lose work than to keep going in a direction that isn't working

3. You'll be busy but be reading other books as much as you are writing.

4. Wake up early or stay up late, 0 distractions is the best for writing

5. Talk out loud, like youre presenting to an audience to get unstuck from writers block.

6. Get feedback as soon as possible.

Marketing the book:

1. If you can, get in writing what marketing they will do for the book.

2. Negotiate on how many free books you can get to give away

3. Sales on Amazon are important, direct sales there, esp on launch day.

4. Start a newsletter (yay more writing!)

Other:

1. This is a second job

2. It does open a lot of doors

3. Consider a co-author for your first book. I added one towards the end and wish I had done it sooner. Its easier to collaborate and bounce ideas off each other and keep each other accountable.

Hey all,

I actually cover this story in my book Tragic Design

(http://shop.oreilly.com/product/0636920038887.do)

In my opinion, the software bug wasn't to blame but bad user interface design. When the error occurred that caused patients to get a direct blast of 10x rad more than what were supposed to get, the error was caught and displayed. But because there were so many erroneous errors, users were used to bypassing them. I go into much more detail in the book but I thought I'd chime in here. What do you all think?