Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Turning Passion Into Words

1,590 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Turning Passion Into Words

  1. 1. Turning Passion Into Words Tips, Tools, Techniques for Aspiring Authorstwitter: bphoganemail: brianhogan at napcs.com
  2. 2. http://www.flickr.com/photos/jjpacres/3293117576/why do we write?
  3. 3. http://www.flickr.com/photos/gemmacowan/303427032/But do people even read books anymore?
  4. 4. Yes. Very yes. http://www.flickr.com/photos/30743345@N04/4694171907
  5. 5. "But people can get all that off of blogs!"
  6. 6. The reader wants yourexperience, not your answers.
  7. 7. Let’s assume you have a topic.
  8. 8. Understand your audience
  9. 9. Define your target audience and decide who is outside
  10. 10. Create a reader profileTammy is a backend software developer She worksprimarily with Java. Shes great with VIm, knows how toconfigure Tomcat with XML, and understands how tough itcan be to get requirements out of users, but when itcomes to picking colors, fonts, or layouts, she needs help.She wants to be able to understand design concepts sothat her conversations with the UI team will go moresmoothly.
  11. 11. Connect with your reader
  12. 12. Dreyfus Model (of skill acquisition)"The Dreyfus model describes howand why our abilities, attitudes,capabilities, and perspectiveschange according to skill level." -Andy Hunt
  13. 13. NovicesNo previous experience, need recipes to solve problems.
  14. 14. 10 years of experienceor one year of experience ten years in a row?
  15. 15. Advanced Beginners They can try tasks on theirown, but they still have difficulty troubleshooting. They want information fast.
  16. 16. CompetentCan develop conceptual models of the problem domain, troubleshooteffectively, and implement their own novel solutions.
  17. 17. Proficient They need the big picture and wantto understand the framework around the skill.
  18. 18. The expertExperts are the primary sources of knowledge and information in any field.
  19. 19. Experts are rare.1-5% of the population
  20. 20. Experts work from intuition and they often cannot explain how they do what they do.
  21. 21. Which one of these are you?
  22. 22. The competent make the best teachers
  23. 23. Most people stop progressing at Advanced Beginner.
  24. 24. Learn about this modeland use it to move your reader from one stage to the next.
  25. 25. Define your thesis!What are you talkin about??
  26. 26. HTML5 and CSS3 are the future of webdevelopment, but you don’t have towait to start using them. Even thoughthe specification is still indevelopment, many modern browsersand mobile devices already supportHTML5 and CSS3. This book gets youup to speed on the new HTML5elements and CSS3 features you canuse right now, and backwardscompatible solutions ensure that youdon’t leave users of older browsersbehind.
  27. 27. Outline your writing 1. HTML5 Forms 1.New form fields 1.Email, url, tel, number, range, date, color 2.discuss fallbacks 1.implement fallback with jquery-ui for calendars 2.discuss modernizr 3.Placeholder and Autofocus 1.Placeholder 1.Placeholder fallback with custom plugin
  28. 28. What do you want the reader to learn? Set goals at the start and see if you meet them at the end.
  29. 29. Research your market• What books out there are similar to yours?• Why would yours be different?• What is your audience size?• How many of them would buy a book on the topic?• What other books would have similar sales numbers to yours?
  30. 30. Your first chapterand don’t start with “Introduction!”
  31. 31. Write about what you are excited about first to gain momentum.
  32. 32. Writing about CodeThe best books about code talk more aboutthe why than the how.Don’t just explain the code. Explain whythe code you’re demonstrating is the bestsolution.
  33. 33. AVOID APPEAL TO AUTHORITYBe the expert Don’t use quotes from well-known people to bolster your argument.Use your experience!
  34. 34. Get into a pattern
  35. 35. http://750words.com/
  36. 36. Be consistent. Try to do a chapter in two weeks.
  37. 37. Voicesetting the tone.
  38. 38. Be yourself.Don’t be funny if you’re not.
  39. 39. Beware of emulationDon’t write like you think you should write or how you see others write.
  40. 40. AcademicBehavior driven development (or BDD) is an agile softwaredevelopment technique that encourages collaboration betweendevelopers, QA and non-technical or business participants in asoftware project. It was originally named in 2003 by Dan North[1]as a response to Test Driven Development, including AcceptanceTest or Customer Test Driven Development practices as found inExtreme Programming. It has evolved over the last few years[2].
  41. 41. Less AcademicBehavior driven development is a software developmentmethodology created by Dan North in 2003 as a responseto traditional Test Driven Development. It includeselements of Extreme Programming, such as acceptancetesting, and it encourages collaboration between technicaland non-technical members of a software developmentteam.
  42. 42. Say more with less• “Utilize” should be “Use”• “At this point in time” should be “Now”• “What x does is...” - just tell us already!• “really”, “very”, “quite”, “severely” don’t emphasize things as much as you think they do. Look for them, remove them, and see if you like how it looks.
  43. 43. Compare:There are twenty-five students who have already expressed a desire to attendthe program next summer. It is they and their parents who stand to gain themost by the government grant.Twenty-five students have already expressed a desire to attend theprogram next summer. They and their parents stand to gain the mostby the government grant.
  44. 44. So you have an idea,a thesis, an outline, some content that we’ve written and self- edited... let’s get published.
  45. 45. Finding a publishervs Self Publishing
  46. 46. Benefits of Traditional Publishers
  47. 47. They have a brand.
  48. 48. They have people to help you • Developmental editors • Copy editors • Professional indexers • Production managers • Marketers • Artists • Professional Typesetters • Foreign Rights brokers
  49. 49. They are also moreexperienced than you
  50. 50. You get a lot of help...but it comes at a cost.
  51. 51. The AdvanceNot always a good deal.
  52. 52. $10,000 advance, 10% royaltiesIf your book doesnt sell, you did a years worth of work for $10,000
  53. 53. Buybacks Publishers have to buy back yourbooks from Amazon if they dont sell.
  54. 54. Self publishing Go it alone?
  55. 55. Can you1. write a concise book that meets the needs of your reader, reasonably free of errors?2. get an unbiased opinion of your work?3. deliver your book in print form to those that want it?4. deliver your book in PDF, ePub, or Kindle format in a way that actually looks good across multiple platforms and devices?5. be willing to promote the hell out of your book through web sites, user groups, communities, trade shows, etc?
  56. 56. Of course you can.But do you have the time?
  57. 57. Finding a publisher• Start with a publisher you respect.• Each publisher has a different process, but most publishers have acquisitions editors that work to find authors for topics. – http://pragprog.com/write-for-us/ –
  58. 58. Developmental Editors Your pair.
  59. 59. A good DE can• Be a sounding board for your ideas and help you find your target audience• Give you feedback as an outsider on your content• Help you keep your tone consistent• Help you stay on track
  60. 60. Copy EditorYoull want one.
  61. 61. Tools to get stuff done
  62. 62. Version controlTreat your book just like code. Its valuable.
  63. 63. A writing tool
  64. 64. XAvoid MS Word.
  65. 65. Markdown plain text to HTML
  66. 66. Extending Ruby============Instead of using monkeypatching, we caninclude our codeas a *module*. module NinjaBehavior def attack puts "Youve been silently killed" end endWe can then bring this behavior into ourclasess. Thistechnique is often called a *mixin*.
  67. 67. You can convert Markdown to HTML and PDF with relative ease.
  68. 68. Markdown does not convey meaning.
  69. 69. Docbook the revenge of XML
  70. 70. XML is only evilwhen you use it wrong.
  71. 71. Docbook features• Descriptive markup• Automatic chapter and section numbering• Automatic cross-referencing• Table of Contents generation• Support for indexing• Extendable• Complete separation between content and presentation• Export to HTML, PDF, ePub, etc
  72. 72. Docbook example<chapter xmlns="http://docbook.org/ns/docbook" xml:id="models.association.ext"><title>Using Association Extensions to group records</title> <para> Association extensions let us apply methods to our ActiveRecord associations so we can quickly get access to your collected data. </para> <para> Our registration system needs a report of all currently enrolled students in a given workshop. We can do that fairly quickly by defining our own <methodname>currently_enrolled</methodname> method on the <classname>Workshop</classname> class like this:. </para> <programlisting language=”ruby”> <![CDATA[ class Workshop < ActiveRecord::Base has_many :enrollments has_many :students, :through => :enrollments def currently_enrolled enrollments.find_all_by_enrolled(true) end end ]]> </programlisting>
  73. 73. Structural markup• chapter – sect1 • sect2 – sect3 – para – orderedlist • listitem – para – unorderedlist • listitem – para
  74. 74. Verbatim markup• programlisting – CDATA • code• screen – CDATA • plain text
  75. 75. Admonishment markup• sidebar• warning• tip• note• caution
  76. 76. semantic markup• application • database • mousebutton• methodname • email • option• varname • errorname • keycombo• classname • errortext • quote• abbrev • foreignphrase • task• acronym • funcparams • term• action • funcdev • uri• arg • interface • ...more
  77. 77. By using this markup, we can create a style guide.
  78. 78. XSLT transformations• HTML• Formatting objects (XSL-FO) – PDF – mobi• ePub
  79. 79. Docbook demo?https://github.com/napcs/docbook
  80. 80. Feedback
  81. 81. Promotion
  82. 82. You have to promote your book• Twitter• Facebook• Your blog• Your reviewers• Amazon reviews
  83. 83. What if I can’t do it all?
  84. 84. Divide up the work get a co-author
  85. 85. Beware though....• You want a unified voice• You need to deal with your disagreements• You need to work as a partnership
  86. 86. Not writing a book? Everything here still applies.
  87. 87. Other questions?

×