<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Amy Hodler on Medium]]></title>
        <description><![CDATA[Stories by Amy Hodler on Medium]]></description>
        <link>https://medium.com/@amy.hodler?source=rss-e04b5980e74e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Uzfy2CHAYP60Ngw4.</url>
            <title>Stories by Amy Hodler on Medium</title>
            <link>https://medium.com/@amy.hodler?source=rss-e04b5980e74e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:32:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amy.hodler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Graphy Math Magic — Simplify Hard Problems]]></title>
            <link>https://medium.com/knowledge-bytes/graphy-math-magic-simplify-hard-problems-e020ab1db188?source=rss-e04b5980e74e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e020ab1db188</guid>
            <dc:creator><![CDATA[Amy Hodler]]></dc:creator>
            <pubDate>Tue, 26 Jul 2022 15:55:05 GMT</pubDate>
            <atom:updated>2022-07-26T15:55:05.345Z</atom:updated>
            <content:encoded><![CDATA[<h3>Graphy Math Magic — Simplify Hard Problems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*45TxPcEjN8prNNV-EaqcTA.jpeg" /></figure><p>Graphy math lets you do some cool tricks but can be tricky. For example, the traveling<strong> </strong>salesman (person) problem (TSP) is a classic graph problem that asks, “Given a list of cities and the distances between each pair of cities, what is the shortest possible route that visits each city exactly once and returns to the origin city?”</p><p>TSP-like questions are found in areas from logistics and scheduling to DNA sequencing. Solving these problems are powerful but you can imagine the number of comparisons you’d have to make to find all the possible shortest paths and find an anwer! That makes these problems very computationally challenging but there are some ways to speed things up.</p><p>A recent post, <a href="https://relational.ai/blog/loopy-lattices">Loopy Lattices</a>, by my colleague @Max.DeMarzi explains how a system built with recursive logic <strong>reduced the time to calculate these multi-path calculations by orders of magnitude</strong>. He states, “Once you are able to think recursively, many problems become a lot easier.”</p><p>Then in his next post, <a href="https://relational.ai/blog/loopy-lattices-and-recursion">Loopy Latices and Recursion</a>, he walks through how the logic in RelationalAI actually works to do this. This is a fun and insightful post, but if you’re like, you just gotta get paper and pen out to follow along. Do this yourself, and you’ll see how a system built on iteration and recursion can simplify even the ‘NP-Hardest’ of problems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e020ab1db188" width="1" height="1" alt=""><hr><p><a href="https://medium.com/knowledge-bytes/graphy-math-magic-simplify-hard-problems-e020ab1db188">Graphy Math Magic — Simplify Hard Problems</a> was originally published in <a href="https://medium.com/knowledge-bytes">knowledge-bytes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are Graphs? A Modern Perspective]]></title>
            <link>https://medium.com/knowledge-bytes/what-are-graphs-a-modern-perspective-1e0959d5c86d?source=rss-e04b5980e74e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e0959d5c86d</guid>
            <category><![CDATA[euler]]></category>
            <category><![CDATA[graph-theory]]></category>
            <dc:creator><![CDATA[Amy Hodler]]></dc:creator>
            <pubDate>Fri, 15 Apr 2022 23:16:11 GMT</pubDate>
            <atom:updated>2022-04-15T23:18:15.618Z</atom:updated>
            <content:encoded><![CDATA[<p>Graphs and network science have held sway over me for the last 7 years because they are the best avenues for understanding and modeling our complex world.</p><p>I’m often asked, “what’s a graph?” After years of launching into tediously interesting detail, I realize most people are searching to understand the modern implications. In honor of the founder of graph theory, <a href="https://www.newworldencyclopedia.org/entry/Leonhard_Euler">Leonhard Euler</a>, who was born on April 15, 1707 (just a wee bit of tedium!), the below is an attempt to answer that question from a contemporary perspective.</p><p>This is an excerpt from work that <a href="https://medium.com/u/68584b0be0fb">Mark Needham</a> and I created a few years ago in the book “Graph Algorithms,” published by O’Reilly Media, Inc. copyright 2019.</p><p>________________________________________________________________</p><p><strong>What Are Graphs?</strong></p><p>Graphs have a history dating back to 1736, when Leonhard Euler solved the “Seven Bridges of Königsberg” problem. The problem asked whether it was possible to visit all four areas of a city connected by seven bridges, while only crossing each bridge once. It wasn’t.</p><p>With the insight that only the connections themselves were relevant, Euler set the groundwork for graph theory and its mathematics. Figure 1–1 depicts Euler’s progression with one of his original sketches, from the paper “Solutio problematis ad geome‐ triam situs pertinentis”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*RoMYqiv5DtpAmlbfapg2WA.png" /><figcaption><em>Figure 1–1. The origins of graph theory. The city of Königsberg included two large islands connected to each other and the two mainland portions of the city by seven bridges. The puzzle was to create a walk through the city, crossing each bridge once and only once.</em></figcaption></figure><p>While graphs originated in mathematics, they are also a pragmatic and high fidelity way of modeling and analyzing data. The objects that make up a graph are called nodes or vertices and the links between them are known as relationships, links, or edges. We use the terms <em>nodes </em>and <em>relationships </em>in this book: you can think of nodes as the nouns in sentences, and relationships as verbs giving context to the nodes. To avoid any confusion, the graphs we talk about in this book have nothing to do with graphing equations or charts as in Figure 1–2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*ivlLxXgP-lL1XvolBlYQWA.png" /><figcaption><em>Figure 1–2. A graph is a representation of a network, often illustrated with circles to represent entities which we call nodes, and lines to represent relationships.</em></figcaption></figure><p>Looking at the person graph in Figure 1–2, we can easily construct several sentences which describe it. For example, person A lives with person B who owns a car, and person A drives a car that person B owns. This modeling approach is compelling because it maps easily to the real world and is very “whiteboard friendly.” This helps align data modeling and analysis.</p><p>But modeling graphs is only half the story. We might also want to process them to reveal insight that isn’t immediately obvious. This is the domain of graph algorithms.</p><p><strong>What Are Graph Analytics and Algorithms?</strong></p><p>Graph algorithms are a subset of tools for graph analytics. Graph analytics is something we do — it’s the use of any graph-based approach to analyze connected data. There are various methods we could use: we might query the graph data, use basic statistics, visually explore the graphs, or incorporate graphs into our machine learn‐ ing tasks. Graph pattern–based querying is often used for local data analysis, whereas graph computational algorithms usually refer to more global and iterative analysis. Although there is overlap in how these types of analysis can be employed, we use the term <em>graph algorithms </em>to refer to the latter, more computational analytics and data science uses.</p><p>Graph algorithms provide one of the most potent approaches to analyzing connected data because their mathematical calculations are specifically built to operate on relationships. They describe steps to be taken to process a graph to discover its general qualities or specific quantities. Based on the mathematics of graph theory, graph algorithms use the relationships between nodes to infer the organization and dynamics of complex systems. Network scientists use these algorithms to uncover hidden information, test hypotheses, and make predictions about behavior.</p><p>Graph algorithms have widespread potential, from preventing fraud and optimizing call routing to predicting the spread of the flu. For instance, we might want to score particular nodes that could correspond to overload conditions in a power system. Or we might like to discover groupings in the graph which correspond to congestion in a transport system.</p><p>In fact, in 2010 US air travel systems experienced two serious events involving multiple congested airports that were later studied using graph analytics. Network scientists P. Fleurquin, J. J. Ramasco, and V. M. Eguíluz used graph algorithms to confirm the events as part of systematic cascading delays and use this information for corrective advice, as described in their paper, “Systemic Delay Propagation in the US Airport Network”.</p><p>To visualize the network underpinning air transportation Figure 1–3 was created by Martin Grandjean for his article, “Connected World: Untangling the Air Traffic Network”. This illustration clearly shows the highly connected structure of air transportation clusters. Many transportation systems exhibit a concentrated distribution of links with clear hub-and-spoke patterns that influence delays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*A59s4k3vGmq0pzhRXSyP8g.png" /><figcaption>Figure <em>1–3. Air transportation networks illustrate hub-and-spoke structures that evolve over multiple scales. These structures contribute to how travel flows.</em></figcaption></figure><p>Graphs also help uncover how very small interactions and dynamics lead to global mutations. They tie together the micro and macro scales by representing exactly which things are interacting within global structures. These associations are used to forecast behavior and determine missing links. Figure 1–4 is a foodweb of grassland species interactions that used graph analysis to evaluate the hierarchical organization and species interactions and then predict missing relationships, as detailed in the paper by A. Clauset, C. Moore, and M. E. J. Newman, “Hierarchical Structure and the Prediction of Missing Links in Network”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*b6Uxh2isNA9kocxhd-UTHQ.png" /><figcaption>Figure <em>1–4. This foodweb of grassland species uses graphs to correlate small-scale interactions to larger structure formation</em></figcaption></figure><p>________________________________________________________________</p><p>I hope that provides a little background to graphs and why so many of us are obsessed with them. Happy birthday Euler and long live graphs!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e0959d5c86d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/knowledge-bytes/what-are-graphs-a-modern-perspective-1e0959d5c86d">What are Graphs? A Modern Perspective</a> was originally published in <a href="https://medium.com/knowledge-bytes">knowledge-bytes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Survival Strategies for Completing Your O’Reilly Book]]></title>
            <link>https://medium.com/@amy.hodler/7-survival-strategies-for-completing-your-oreilly-book-6ee247b0e9a1?source=rss-e04b5980e74e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee247b0e9a1</guid>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[technical-writing]]></category>
            <dc:creator><![CDATA[Amy Hodler]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 21:24:00 GMT</pubDate>
            <atom:updated>2020-02-26T21:24:00.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oF63Xu8gwY4tWQNhMLe2WQ.jpeg" /><figcaption>From the O’Reilly Book: Graph Algorithms</figcaption></figure><p>How do you survive <em>completing</em> an O’Reilly book? If you’re thinking about authoring a technical book, have just signed a contract to do so (congrats!), or are part way through your writing — some variation of this question is on your mind. In a nutshell, it’s hard and gratifying, and there are a few skills that will result in a more rewarding experience.</p><p>Earlier this year, O’Reilly published the book <a href="https://www.amazon.com/Graph-Algorithms-Practical-Examples-Apache/dp/1492047686/">Graph Algorithms: Practical Examples in Apache Spark and Neo4j</a> authored by <a href="https://medium.com/u/68584b0be0fb">Mark Needham</a> and me. (You can get a <a href="https://neo4j.com/graph-algorithms-book/"><strong>free copy here</strong></a><strong> through April 15th</strong> this year.)</p><p>Since publishing the book, we’ve had quite a few questions from would-be authors that range from the “return on effort” to writing tips and concentration techniques. We put our heads together and deliberated on the common threads that run through these questions, what was most useful for us, and what we’d do differently.</p><p>Based on Mark’s and my experience, we’ve grouped 7 Strategies we believe will assist you in completing a technical book. In summary:</p><p><strong>1. Foster internal motivations</strong>, so you can appreciate the process and weather the tough days and tedious tasks.</p><p><strong>2. Balance schedules with reality</strong> so that you have defined deadlines with built-in buffers for the unexpected.</p><p><strong>3. Ruthlessly focus</strong> on the book with regular habits and increase the time block as you progress.</p><p><strong>4. Embrace the art of writing </strong>with a reader foremost in your mind.</p><p><strong>5. Get comfortable with a few processes</strong> and tools to keep you on track, but don’t worry about finding the “perfect” approach (it doesn’t exist.)</p><p><strong>6. Pay attention to examples and illustrations</strong> along the way, so they don’t overwhelm you later.</p><p><strong>7. Get good at asking for help</strong> that brings in the expertise you lack and encourages critical review.</p><p>We put a bit of thought into helping our other authors and have detailed each of these strategies below.</p><h3>1. Foster Internal Motivation</h3><p>Several months into the project, when the code isn’t working and other deliverables are late, you’ll want to remember why you were excited in the first place. Be clear (and honest) about your motivations for authoring a book. If external factors are your only drivers, ask yourself what happens if those don’t materialize. Evaluate what else there is to gain, such as knowledge, new abilities, and the chance to test out ideas.</p><p>Although writing a book can be very rewarding, it’s not likely to be financially equivalent to the time you put in. We recommend considering more intrinsic motivations. Being an O’Reilly co-author has been a fantastic boost to my credibility and career, but that didn’t get me through some of the more frustrating days.</p><p>I’ve always enjoyed research and want to author a science-history book someday. The O’Reilly opportunity gave me the chance to understand this process as well as learn more about a topic I love. Enjoying the process was vital for keeping me motivated. (As a side note, Mark and I both admit to being very sad with “empty book syndrome” when finally done. Don’t worry; it gets better after a week or so.)</p><p>Internal motivations will help you get through tough days and less exciting tasks.</p><h3>2. Balance Schedules with Reality</h3><p>It’s critical to have a committed schedule and committed time to get things done. As most gurus of getting organized will tell you, break things down into smaller, more manageable tasks. Mark and I mapped out specific topics and chapters to approximately 2-week increments and communicated our schedule to our editor as well as colleagues. This framework was essential for planning other work and commitments.</p><p>Initially, we did reasonably well with keeping our schedule with dedicated time each day for the work. (We cranked out a new chapter every two weeks for the first six chapters!) However, we didn’t plan for the unexpected. For example, we re-arranged content for better flow in the first three chapters, which took us three weeks, and later we lost another 3–4 weeks due to a dataset-test problem. Above what you already have planned, I’d recommend adding extra time for reworking drafts, perhaps two weeks midway and again towards the end. If you’re testing new concepts or data, add 2–3 weeks to work out problems.</p><p>There are also multiple phases of being “done” and various definitions of doneness. Never having worked with a publisher, this confusion led us to believe we were “just about” done several times. Ask for detail about the typical timing for different phases and check your projections against the publisher’s estimates: your first draft writing pace and code testing; editorial reviews of each chapter; content reviews; rework of material; external or 2nd expert review; illustration work and reviews; final grammar and style reviews; the digital review; and final print layout reviews.</p><p>Remember, you are not a machine. Mark or I didn’t plan well for running out of steam, and “life happens” events. We dealt with the unexpected by picking up the slack. That may work on the calendar, but you’re going to need some breaks. Explicitly add vacation time to your plan or your content will suffer as you progress. And if you’re generally on-schedule, your editor and colleagues will be more accommodating if (when!) you need to make adjustments.</p><h3>3. Ruthlessly Focus</h3><p>Learning to focus is the single, most important skill you can develop if you’re going to complete a book. An unwavering focus will make you immensely more productive and creative. It may take practice, but with that kind of concentration, will you author a better book and maintain your sanity.</p><p>If you struggle to focus, check out this video on <a href="https://www.youtube.com/watch?v=ZD7dXfdDPfg">Deep Work</a>, which is also a book by Cal Newport, for simple strategies to get started. (I love his advice to “be lazy” at specific times.)</p><p>For our situation, Mark and I knew there were some distractions we could eliminate. We closed Slack and email during scheduled writing days and used a back-channel to communicate with each other. We also found it easier to dedicate an entire day to research and writing versus trying to work on the book for a few hours every day. We focused about three days a week for the first ½–¾ of the book (June-September) and then increased that to finish the book.</p><p>Habits or rituals are another focus hack. Exploring and doodling about difficult concepts helps me to first internalize ideas. And a quick walk helps clear my head and get ready to sit down and write.</p><p>Also, figure out your work rhythms and protect the time when you are most productive. It may not be apparent at first, but pay attention to when you have more energy for the book and when it feels like a slog. I’m most writing-productive from 10 am to 2 pm.</p><p>It can be hard at first to spend hours on a task or say “no” to requests, but you’ll get better at focusing overtime. Plan your strategies, have responses on hand, and be ruthless in what you don’t do.</p><h3>4. Writing Matters — Embrace It</h3><p>Having knowledge is not enough, and your expertise will not magically translate into a book that people can use. I cringe when someone says they think they’ll hire a ghostwriter to speed up the process. Writing matters in a book (I can’t believe I’m saying that), so you can’t skip or glide over it. Also, a book is a long-form format that has different requirements than our daily email, Slack chats, and blogs. Take this difference seriously and embrace it as another skill you get to improve. There are many writing resources, so you should be able to find something that suits you. I recommend the classic, <a href="https://www.amazon.com/Writing-Tools-Essential-Strategies-Writer/dp/0316014990">Writing Tools</a> by Roy Peter Clark, and Mark really liked <a href="https://www.goodreads.com/book/show/53343.On_Writing_Well">On Writing Well</a> by William Zinsser and <a href="https://www.goodreads.com/book/show/20821371-the-sense-of-style">The Sense of Style</a> by Steven Pinker.</p><p>In regards to technical writing, spend extra time working out how you’re going to explain things from a reader’s perspective and what they most likely need. Acknowledge that you know much more than the reader and explicitly define concepts, create bridges between ideas, and use stories or metaphors. While the use of examples and stories can sometimes feel superfluous to a writer, readers need mental breathing room to let concepts sink in. It’s a balancing act so look for early feedback to help you get the feel for it.</p><p>Our editor kept reminding us to leave conceptual bread crumbs: Introduce what we’re about to cover; periodically tell the reader where they are in the flow, and then summarize at the end. That may feel redundant, but it makes reading easier for skimmers and anyone that doesn’t read a chapter straight through in one sitting — which is probably everyone. Also, we rewrote every introduction to every chapter. Wait to complete your introduction and use a simple outline for reference.</p><p>Resist the temptation of tangents (or at least most of them.) Ask yourself if a fascinating concept you’ve just dived into is necessary for the reader at this time. If you’re not ready to explain an idea in detail, introduce it later when you are ready. We made this mistake in several areas of our first draft with a bunch of forward-references. Having a lot of short teasers with “we’ll talk about this later,” quickly became frustrating to our reviewer and required a significant amount of rework.</p><p>Finally, assume the readers are interested in the topic. If they picked up the book, you don’t have to justify yourself that much. If you spend too much time on the background material, people will either lose confidence or get bored waiting for the meat. Make sure there’s intellectual and practical pay-off early in a technical book.</p><p>In summary, it’s not about you — it’s about the reader.</p><h3>5. Get Comfortable with a Few Processes</h3><p>Having a process is more important than which one(s) you choose to employ. There are many tools and techniques you can use to keep on track and make things easier for yourself. As someone prone to overthinking things, I’d recommend limiting your research time and then just picking a few methods.</p><p>We used the O’Reilly Atlas authoring platform because it made the publishing process a bit easier for them, and it allowed us to bounce between HTML and AsciiDoc formats. With all the iterative reviews, I quickly came to appreciate the Atlas tool’s ability to easily create PDF versions that mimicked the published output. Most authoring platforms seem reasonably flexible, so prioritize features that align to your expected workflow.</p><p>In organizing our thoughts, we followed a typical outline approach where we’d talk through the flow and then add more detail as well as proof points. It wasn’t always perfect, but it gave us a starting point we could storyboard. On occasion, I also used a more “analog” approach sketching ideas on a whiteboard or large pad to work with less linear bias.</p><p>A simple Google Doc served us well to keep track of all the backlog questions or changes we had for each chapter. We’d review our outstanding items almost daily, discuss how to deal with them, and then tick them off when complete. This simple process allowed Mark and I to keep going with the task at hand while not losing track of issues. (Note that this also aids in keeping you focused.)</p><p><a href="http://www.grammarly.com/">Grammarly</a>, an online grammar tool, became indispensable for me in finding my common mistakes and overuse of certain words. (Apparently, I <em>really</em> like the word, “cluster.”) At the very least, use the free version of Grammarly to find silly typos and keep your editors from being distracted from more meaningful review.</p><p>Any new tools and processes take some time to get comfortable with, and what may feel awkward now may save you a lot of effort later.</p><h3>6. Pay Attention to Examples and Illustrations Along the Way</h3><p>It’s often the little things you plan to fix later that surprisingly add up. There are a few areas of content that “crept up” on us late in the process that you might be able to reduce or avoid.</p><p>First, set aside time to evaluate examples, datasets, and use cases for use throughout the book. Having a common scenario makes it easier for the reader to follow and saves you time in explaining multiple examples. The next best option is to limit yourself to one example set per chapter. Perhaps this seems obvious, but in a rush to get started, it’s easy to think that you’ll work out the details in other sections later.</p><p>If you’re referencing other research and work in the book, try to obtain approval for inclusion as you work through each chapter. Even if the content is public, this illustrates your respect for their work and allows you to ask additional questions or gather feedback on ideas along the way. Offering to send a copy of the book once completed, is an excellent way to show your appreciation.</p><p>For your code samples, make sure to complete any tweaks before the book enters digital production and double-check column width restriction for the print production. The difference in digital and print page layouts can cause unexpected results such as line wrapping in code and illustration surprises. Don’t assume you’re done just because the digital edition looks fine. And to save effort later, find ways to make your code more accessible, like using Docker so that others can more readily reproduce your results.</p><p>And then we have illustrations. A lot of people are visual learners, so they need clear, consistent illustrations. We created a lot of unpolished diagrams and charts with the intent of polishing later. At the end of the first full draft, we had a very rough-looking book. Luckily, we were able to call in some favors to standardize the style, but I highly recommend that you do not leave your illustrations to the end. In our case, by chapter 2 or 3 we could have paused to work out an illustration template that would have saved time later. Ask your publisher for their guidelines but test a few styles early for their effect in color, black and white, and at a much smaller size than you expect.</p><h3>7. Get Good at Asking for Help</h3><p>You’re the expert, but not of everything. Learn to ask others for help, even before you need it. It’s a lot of work to complete a book, so expect that you’re not going to know everything or have time to figure it all out.</p><p>First, think about collaboration with a co-author. I loved working with my co-author, Mark. We are both easy going but with very different abilities and ways of interpreting things. It was advantageous for one of us take the lead on a chapter and have the other editing or clarifying or adding stories. Having a co-author keeps you honest about your commitments. Mark is in London and I’m in Washington state. We talked almost every morning to review issues, plans, and pass material back and forth. This schedule kept the pace moving and I knew if I didn’t get my tasks done that day, it would put Mark behind the next day.</p><p>Expect your editor to give you structural advice, not content feedback. Our O’Reilly editor, Jeff Bleiel, was terrific, but he wasn’t an expert in graph algorithms. (I still hear Jeff in my head when I review material today.) We had two vital Neo4j reviewers, Michael Hunger and Jim Webber, that gave us extensive feedback at several points in the book. They were extremely familiar with the material but had very different styles. We also reached out to several individuals with particular expertise as well as friends at GraphAware for comments. At some point, you will become blind to omissions, tangled ideas, and tortuous phrases — you just read over them. External, critical reviewers are the only way to uncover these problems.</p><p>Plan to ask colleagues or community members if they would be willing to assist (especially with reviews), but be respectful of their effort. Try to modularize their efforts, and consider when it may be appropriate to compensate an expert for their review or an illustrator for their polish.</p><h3>Final Thoughts</h3><p>Most people find authoring a book a lot of work, especially those of us that aren’t professional writers. It can be challenging to know what’s important (so many choices), tiresome to foster a new routine, and frustrating when things aren’t coming together. And yet, it was one of the most rewarding things I’ve done. Mark and I agree that the overall process of research, testing, and narrative was thoroughly enjoyable, and we look forward to tackling another book someday.</p><p>We hope that sharing our 7 Strategies will assist others in completing their technical book and enjoying the process.</p><p>Let us know if these are useful and please comment with your tips so we can all learn!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee247b0e9a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>