<?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 Jeff Terrell PhD on Medium]]></title>
        <description><![CDATA[Stories by Jeff Terrell PhD on Medium]]></description>
        <link>https://medium.com/@kyptin?source=rss-4a895faf4df1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3QgIpsVptq5SK-Ul.jpg</url>
            <title>Stories by Jeff Terrell PhD on Medium</title>
            <link>https://medium.com/@kyptin?source=rss-4a895faf4df1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:17:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kyptin/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[DevOps is a Big Deal and what you should know about it!]]></title>
            <link>https://medium.com/rolemodel-software/devops-is-a-big-deal-and-what-you-should-know-about-it-5b6fd8e3cd87?source=rss-4a895faf4df1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b6fd8e3cd87</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Jeff Terrell PhD]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 13:30:11 GMT</pubDate>
            <atom:updated>2018-08-03T13:30:11.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhBN7BcbPcXzNoxpcIOuRA.png" /><figcaption>Understanding DevOps can accelerate the success of your System of Software</figcaption></figure><p>If you’re in tech, you’ve probably been hearing the term “DevOps.” What’s all the fuss about? DevOps is more than a trendy synonym for IT. In a nutshell, DevOps is the integration of software development and IT to enable impressive scale, agility, and delivery of value through software. I’ll unpack below what that means and why we should care. Along the way, we’ll see how DevOps connects with business and technical agility, collaboration, and success.</p><h4>Agile Roots</h4><p>In 2011, Venture capitalist Marc Andreessen famously said that <a href="https://a16z.com/2016/08/20/why-software-is-eating-the-world/">software is eating the world</a>. His idea is that software enables people and companies to do their jobs better and deliver value faster. These software-enabled companies are more agile than companies that don’t use software (or don’t use it well), and this agility enables them to move and pivot faster. As a result, software-enabled companies will win in the long run. Eventually, using software well will be a basic requirement of entering the marketplace. If you’re not doing software, you’re going to lose.</p><p>Just as software enables agility, developing software in an agile way outperforms traditional, planning-heavy methods such as the waterfall approach (as RoleModel Software’s founder and CEO, Ken Auer, lays out in his <a href="https://www.amazon.com/Extreme-Programming-Applied-Playing-Win/dp/0201616408">book</a>). Agile responds better to change and change is almost always required. Agile methods such as Extreme Programming, Scrum, and Kanban are gaining mindshare among professionals and at many companies Agile methods are accepted as the way work gets done. At RoleModel Software, we believe that agile software wins and that an agile, collaborative approach will be “table stakes” for companies competing in the marketplace. In short, if you’re not doing software <em>in an agile way</em>, you’re going to lose.</p><p>What does this have to do with DevOps? Bear with me for one more context-setting excursion.</p><h4>The System of Software</h4><p>Have you ever thought about what software <em>is</em>? Or what is the essence of software? I think software by itself is inert: it’s just bits on a disk somewhere. It needs a system to make it run. That system involves many separate pieces all working together to animate the software. Most software systems, or at least most web applications, include:</p><ul><li>libraries written by other people</li><li>frameworks written by other people</li><li>programming languages and compilers</li><li>web servers and web browsers</li><li>database servers</li><li>operating systems</li><li>machines, whether physical or virtual, with all the associated hardware</li><li>networking infrastructure, including load balancers, routing, SSL, firewalls, domain names, etc.</li></ul><p>The point is that there’s only value in software when the broader system works together.</p><p>DevOps addresses this question: How do we apply the principles of agility not only to the development of the software, but also to the development of the system?</p><h4>Development + Operations = Success</h4><p>At RoleModel Software, we believe we are most effective when we work alongside our customers, understand their experiences and their needs, and collaborate with them on how best to solve their problems while recognizing their context and priorities. This is exactly the idea behind DevOps. Except with DevOps, the people who are collaborating are not consultants and customers, but software developers and IT people. That’s where the term “DevOps” comes from: it’s a combination of Development and Operations.</p><p>In many organizations, especially those that still think of software as a thing to be constructed, like a building, there is a divide between Development and IT Operations. Their idea is that Development should focus on the software and IT should focus on the system, including ongoing monitoring and management responsibility. Unfortunately, a strained if not outright adversarial relationship often results from this division. When things go wrong, it’s easy to point fingers across the aisle without understanding the other side. This breakdown of trust often results in setting up additional heavyweight processes, such as testing and quality assurance, on the pre-deployment side. Deployments become a rare and dreaded occurrence on a quarterly or even yearly basis.</p><p>The idea of DevOps is to bring the collaborative, agile software mindset to the IT department. Developers work to understand the problems that Operations faces and they then collaborate to build tools, automate processes, and solve problems. The developer gains an appreciation of the system and can apply software, the “world eater,” to improve it.</p><p>The goal is to improve the agility of the software system in the same way software has improved the agility of people and businesses everywhere. Then the DevOps-enabled companies can outperform their competition. They respond to changes in the marketplace faster, get feedback from experiments faster, and even fix bugs faster.</p><p>If DevOps is done well, the flow of work from development to production is unimpeded; there are no operational bottlenecks that constrain the flow. The only constraint is the number of developers working on the software. As a result, the number of production deployments can go from one per quarter to many per day. Deploying new code to production becomes a routine, everyday occurrence. A hallmark of effective DevOps practices is that the number of production deployments scales linearly with the number of developers, even with tens of thousands of developers. (This was an unreachable goal 15 years ago!)</p><h4>Proof that DevOps Works</h4><p>All the software companies that are household names already do DevOps; indeed, many of them pioneered these practices. That includes Google, Facebook, Amazon, and Netflix, each of which does multiple production deployments per day. In some cases the rate of change is staggering. In 2015, Amazon revealed that they were doing 130,000 production deployments per day. That’s more than one per second. And that was in 2015. Correlation doesn’t necessarily imply causation, but I believe DevOps is a large part of why they’ve been able to grow as big as they have.</p><p>Furthermore, many analysts have picked up on the fact that DevOps-enabled companies are outperforming the rest. <a href="https://puppet.com/resources/whitepaper/2016-state-of-devops-report">Studies</a> have shown that these companies tend to have much better key performance indicators, ranging from technical (reliability, security, mean time to restore service) to corporate (employee job satisfaction, profitability).</p><h4>What it all means</h4><p>If you’re not currently developing and delivering software systems in an agile way, you’re probably losing. The practices of DevOps can help. RoleModel Software has a history of agility and collaboration and we would love to help you. Consider us for your next custom software project! (And please leave a comment on this post!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b6fd8e3cd87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rolemodel-software/devops-is-a-big-deal-and-what-you-should-know-about-it-5b6fd8e3cd87">DevOps is a Big Deal and what you should know about it!</a> was originally published in <a href="https://medium.com/rolemodel-software">RoleModel Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Docker in Heroku: Understanding the Tradeoffs]]></title>
            <link>https://medium.com/rolemodel-software/using-docker-in-heroku-understanding-the-tradeoffs-48821ba8c6e9?source=rss-4a895faf4df1------2</link>
            <guid isPermaLink="false">https://medium.com/p/48821ba8c6e9</guid>
            <category><![CDATA[software-craftsmanship]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Jeff Terrell PhD]]></dc:creator>
            <pubDate>Wed, 02 May 2018 19:02:12 GMT</pubDate>
            <atom:updated>2018-05-02T19:02:12.089Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*QDplb2kXJYpPIM_fujWY2Q.jpeg" /><figcaption>The new Heroku container runtime is compared to the traditional slug compiler</figcaption></figure><p><em>The following post is technical in nature and assumes familiarity with </em><a href="https://www.docker.com/what-container"><em>Docker and containers</em></a><em>.</em></p><h3>Summary</h3><p>Heroku<a href="https://blog.heroku.com/container-registry-and-runtime?c=7013A000002IMQDQA4&amp;utm_campaign=Newsletter_October_2017&amp;utm_medium=email&amp;utm_source=newsletter&amp;utm_content=blog&amp;utm_term=heroku-docker-images"> recently announced</a> their container runtime, which enables deployment of docker images to Heroku. The overall experience is on par in terms of features and ease with the traditional approach, which uses the <a href="https://devcenter.heroku.com/articles/slug-compiler">slug compiler</a>. It enables greater flexibility and control of your software system, but you assume the responsibility to maintain your system and keep it secure. This post discusses the tradeoffs and reasons to favor one approach over the other.</p><h3>Background</h3><p>At RoleModel, Heroku is our default choice of platform. We’ve found that it consistently saves us significant time in setting up, deploying, and managing the infrastructure that our apps run on. In our mission to deliver value to our customers via software, we’ve found it to be a net win in most cases: the cost of the platform is less than the cost of our time managing infrastructure with a cheaper provider like AWS.</p><p>We are also increasingly taking advantage of Docker in our projects, as it affords good isolation of development environments without sacrificing performance. Similarly, <a href="https://github.com/docker/compose">Docker Compose</a> enables us to specify the entire software system context of one of our apps, making it easy for a developer to spin up on a new project and switch between projects, even those with different versions of tools such as Ruby, PostgreSQL, or Node.js.</p><p>When Heroku<a href="https://blog.heroku.com/container-registry-and-runtime?c=7013A000002IMQDQA4&amp;utm_campaign=Newsletter_October_2017&amp;utm_medium=email&amp;utm_source=newsletter&amp;utm_content=blog&amp;utm_term=heroku-docker-images"> announced</a> their<a href="https://blog.heroku.com/container-registry-and-runtime"> container runtime</a> in October, 2017, we wanted to take a closer look to see if this offering might be an excellent fusion between Docker and Heroku that would deliver value to our customers faster.</p><h3>Heroku’s container runtime</h3><p>The standard deployment to Heroku involves a snapshot of the code in a repository at a given commit. There are two approaches. First, you can use git to push a git commit to a git remote that Heroku owns. Second, you can use Heroku pipelines and Heroku review apps, which are associated 1-to-1 with GitHub pull requests and are aware of new and updated pull requests through GitHub integrations. In either case, Heroku learns of a commit and invokes the slug compiler to create a “slug” for the code at that commit. A slug is analogous to an image in Docker: it contains a static snapshot of everything that will be needed to run the app. The slug compiler identifies which language and framework is being used and invokes the appropriate buildpack to fetch language libraries and package everything together.</p><p>Heroku’s new<a href="https://blog.heroku.com/container-registry-and-runtime"> container runtime</a> offers an alternative: you tell Heroku which Dockerfile in your repo to use for build instructions. This approach will be familiar to Docker users, because Dockerfiles are the same mechanism Docker itself uses to build images. Heroku can then build and deploy your docker image instead of a slug.</p><p>Note that we are using the container runtime in conjunction with the Heroku<a href="https://devcenter.heroku.com/articles/heroku-yml-build-manifest"> build manifest</a> (i.e. heroku.yml). The build manifest, which is currently in developer preview, is what enables Heroku to build and deploy the docker image itself. Without it, many features such as <a href="https://devcenter.heroku.com/articles/pipelines">pipelines</a>, <a href="https://devcenter.heroku.com/articles/github-integration-review-apps">review apps</a>, and the <a href="https://devcenter.heroku.com/articles/release-phase">release phase</a> are not available with Docker-based deployments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlIHVbEM14nZnR_9q1XzGA.png" /><figcaption>An example docker build log, as seen from the Heroku dashboard.</figcaption></figure><h3>Comparison</h3><p>We were interested to know how the container runtime compares with the more traditional approach of the slug compiler and language specific buildpacks.</p><h4>Similarities</h4><p>In many ways, the two approaches are identical. In both cases,you can see that “developer experience” or “DX” is a strong value to Heroku. Here is a list of things I tried that behave the same way, modulo minor differences like whether to specify a configuration setting in Procfile or heroku.yml:</p><ul><li>The<a href="https://devcenter.heroku.com/categories/command-line"> Heroku CLI</a>, including: heroku open to open the deployed app in a browser; heroku logs, which are as helpful as ever; and heroku run bash to run a shell in a production environment isolated from the “dyno formation” of running servers, for things like database migrations or access to a Rails console.</li><li><a href="https://elements.heroku.com/addons">Heroku addons</a>, including <a href="https://elements.heroku.com/addons/heroku-postgresql">Heroku Postgres</a>, <a href="https://elements.heroku.com/addons/honeybadger">HoneyBadger</a>, and <a href="https://elements.heroku.com/addons/newrelic">New Relic</a>, all of which we specifically tested.</li><li>The<a href="https://devcenter.heroku.com/articles/heroku-dashboard"> Heroku dashboard</a>, including configuration and environment variables.</li><li><a href="https://devcenter.heroku.com/articles/pipelines">Pipelines</a>, for a sequence of related apps from staging to production.</li><li><a href="https://devcenter.heroku.com/articles/github-integration-review-apps">Review apps</a>, which are automatically provisioned and track 1-to-1 with GitHub pull requests.</li><li>The<a href="https://devcenter.heroku.com/articles/release-phase"> Release phase</a>, which enables things like database migrations to run whenever a new release is created for your app. (The postdeploy steps in app.json work too, although this is<a href="https://devcenter.heroku.com/articles/release-phase#review-apps-and-postdeploy-script"> not recommended</a> because the postdeploy steps will not be re-run in a review app when new commits are added to the corresponding pull request.)</li><li><a href="https://devcenter.heroku.com/articles/github-integration">GitHub integration</a>, so that review apps in a pipeline can be automatically provisioned and the production code can be continuously deployed from a branch.</li></ul><h4>Differences</h4><p>When comparing the container runtime and the slug compiler, the similarities far outweigh the differences. Nevertheless, it’s worth mentioning the differences too:</p><ul><li>Assuming you want Heroku to assemble your code into something runnable, instead of the traditional Procfile, you use the new<a href="https://devcenter.heroku.com/articles/heroku-yml-build-manifest"> build manifest</a> at heroku.yml, which is structured a bit differently.</li></ul><blockquote>Note: The<a href="https://devcenter.heroku.com/articles/heroku-yml-build-manifest#executing-commands-before-after-compilation"> build manifest documentation</a> says that you can specify commands to run before or after compilation with pre and post keys under the build key. However, as of March 29, 2018, these commands are silently ignored when using a build -&gt; docker key to specify docker-based builds. This behavior is not presently documented, so I wanted to mention it here.</blockquote><ul><li>It’s possible with the container runtime to deploy code without creating a git commit by saying heroku container:push.</li><li>One feature that the container runtime doesn’t currently have, even when combined with the build manifest, is pipeline promotions (we don’t often use this feature, so it is not considered a great loss). I suspect Heroku is working to make them available to container-based deployments too, however, so this may change in time.</li></ul><h3>Analysis of the container runtime</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nRBBcqDlEpExISpRG0fzoQ.png" /><figcaption>The Docker container runtime delivers both advantages and disadvantages to the user</figcaption></figure><h4>Advantages</h4><p>The container runtime has two advantages over the traditional slug compiler and language buildpacks. First, if you’re already using docker in a development environment, you can achieve better parity between the development and production environments. Second, you can have better control over how your software is built.</p><p>However, the quality of the standard Heroku platform has eroded some of these advantages. Parity between development and production environments is valuable because it can avoid problems that only surface when deploying code to production. But such issues almost never happen with Heroku because the platform is designed and engineered well to avoid them. Greater control over the build process is not something we’ve felt a need for when using Heroku. The official buildpacks work sufficiently well that we have never needed to debug or customize them. If you have felt this pain and wrestled with Heroku to get your app deployed then these advantages might be compelling.</p><h4>Disadvantages</h4><p>The primary disadvantage of a container runtime is the classic tradeoff between increased control and increased responsibility. When you use the traditional slug compiler and<a href="https://devcenter.heroku.com/articles/stack"> default Heroku stacks</a>, Heroku is responsible for noticing relevant security updates, upgrading their stacks, and migrating your app to the upgraded stack. When you use the container runtime, Heroku cannot do these things for you. The responsibility falls to you as the application maintainer.</p><p>For short-lived apps or apps where security is not important, this is not a problem. But at RoleModel many of our apps don’t meet these criteria, and we actively benefit from Heroku’s vigilance.</p><h3>Recommendation</h3><p>As we at RoleModel have learned from the <a href="https://www.bumc.bu.edu/facdev-medicine/files/2012/03/Dreyfus-skill-level.pdf">Dreyfus Model of Skills Acquisition</a>, the best course of action depends on the context and the goals. So, while the container runtime might not be a great fit for many of our projects, perhaps your situation is different. Consider using the container runtime when:</p><ol><li>you have experienced problems or anticipate problems related to the disparity between your local development environments and the production Heroku environment;</li><li>you believe that there is enough value in available Docker images to forgo the conveniences of Heroku’s stacks and buildpacks; or</li><li>you spend time or anticipate spending time wrestling with the constraints of Heroku, for example in one of these ways: (a) you use an unusual language that has no officially supported buildpack, like Elixir (although note that there are many<a href="https://elements.heroku.com/buildpacks"> third-party buildpacks</a>, including<a href="https://elements.heroku.com/buildpacks/hashnuke/heroku-buildpack-elixir"> one for Elixir</a>); (b) you need Ubuntu packages beyond<a href="https://devcenter.heroku.com/articles/stack-packages"> what’s already installed on the official stacks</a> (although note that the<a href="https://devcenter.heroku.com/articles/heroku-yml-build-manifest#installing-packages-from-apt"> heroku.yml build manifest</a> and<a href="https://github.com/heroku/heroku-buildpack-apt"> other approaches</a> can also solve this problem); (c) you use a combination of languages in your app (and you don’t want to use<a href="https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app"> multiple buildpacks</a>); or (d) you need to use a non-Ubuntu flavor of Linux for some reason.</li></ol><p>However, if you choose the container runtime, remember that you must assume the associated maintenance responsibility. For this reason, if you don’t have a compelling use case for the container runtime, we recommend the traditional stack as a default.</p><p>Have you had any experience with using Docker on Heroku? We’d love to hear about it. Please leave a comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48821ba8c6e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rolemodel-software/using-docker-in-heroku-understanding-the-tradeoffs-48821ba8c6e9">Using Docker in Heroku: Understanding the Tradeoffs</a> was originally published in <a href="https://medium.com/rolemodel-software">RoleModel Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The divide-and-conquer strategy applied to writing blog posts]]></title>
            <link>https://medium.com/rolemodel-software/how-to-write-a-blog-post-ed58edcdc17c?source=rss-4a895faf4df1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed58edcdc17c</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[creative-process]]></category>
            <dc:creator><![CDATA[Jeff Terrell PhD]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 15:14:31 GMT</pubDate>
            <atom:updated>2017-07-25T20:39:12.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2ackzaK2ixZjrLwDYjmBg.jpeg" /><figcaption>Source: <a href="https://pixabay.com/en/nib-ink-writing-calligraphy-pen-1219010/">https://pixabay.com/en/nib-ink-writing-calligraphy-pen-1219010/</a></figcaption></figure><h3><strong>A guide for linear thinkers</strong></h3><p>A strategic initiative this year for my company, <a href="https://www.rolemodelsoftware.com/">RoleModel Software</a>, is to ‘Tell Our Story.’ We’ve been focused on serving our current customers, but now we’d like to get better at reaching out to potential customers. In keeping with that theme, we are encouraging our team to create more blog posts.</p><p>But writing a blog post is not always easy, especially if you lack experience. Sometimes, “writer’s block” hits you square in the face. Other times, certain emotions provide considerable resistance to writing. I’ve encountered a variety of challenges with writing, and I wanted to share how I’ve dealt with them. I hope that my approach will appeal to programmers and other linear, “<a href="https://www.verywell.com/left-brain-vs-right-brain-2795005">left-brained</a>” people. I’m not an expert writer, but I have some experience <a href="http://blog.altometrics.com/index.php/author/jeff/">blogging</a> and have written a handful of academic papers and <a href="http://www.cs.unc.edu/xcms/wpfiles/dissertations/terrell.pdf">a dissertation</a>. Along the way, I’ve developed a process that works well for me, designed on the principle of dividing a large, unwieldy task into smaller, individually tractable tasks.</p><p>My writing process follows these steps:</p><ol><li>Identify your topic</li><li>Identify your audience</li><li>Research</li><li>Braindump</li><li>Outline</li><li>Draft</li><li>Revise</li></ol><p>I’ll discuss each step of my process in turn. (There’s an implicit “Publish” step afterward, but that’s less about writing, so I won’t discuss it here.) Note that these are not ironclad rules of writing but suggestions of things that work for me.</p><h3>Step 1: Identify your topic</h3><p>The first step is to identify a topic to write about. Sometimes, this is easy. Maybe a friend suggests a topic to you, or maybe you’re working on something interesting and want to share it. In any case, I think a good topic has three essential characteristics:</p><ol><li><strong>You care about it.</strong> If you try to write about something you don’t care about, not only will it be drudgery to write about, but your readers will probably find it toilsome to read, assuming they don’t skip it entirely.</li><li><strong>You understand it (pretty well).</strong> <em>One’s writing is never clearer than one’s thinking.</em> If you don’t understand your topic, your writing will be confused and unhelpful.</li><li><strong>You can identify an audience for it.</strong> If you don’t know who you’re writing to, your writing will be vague, tedious, or both as you try to develop your ideas for different groups at the same time.</li></ol><p>The first of these is the most important because it’s the hardest to overcome if it’s missing. If you don’t understand a topic, you can research it. And identifying an audience doesn’t have to be difficult, as I’ll discuss later. But if you don’t care about a topic, it’s difficult to generate interest in yourself or others. So at the risk of sounding cheesy, follow your heart, and identify a topic that you care about.</p><p>You may disqualify an idea because others have already written about it. But novelty is a difficult goal that few achieve. Besides, it’s OK if others have written about it. Your perspective may be the one that connects with someone in a way the others don’t.</p><h3>Step 2: Identify your audience</h3><p>Closely related to identifying your topic is identifying your audience. Who are you writing to? Who are you hoping to inform, inspire, or entertain?</p><p>The more specific you can be about your audience, the better. In fact, I recommend identifying one person (or at most two or three people) you know, then write specifically to them. When I was writing my dissertation — widely considered the bane of a Ph.D. student’s existence — I found it helpful to write it to my office mate, another grad student in my research group. I could easily tailor what to say, and how much detail to include, by asking the question, “What would I tell Jay?” Whether you tell the person their role or not is up to you (I usually don’t), but at least <em>imagine</em> that you’re writing to them.</p><p>Once you have a person (or three) in mind, I recommend <a href="https://christianedblog.com/2012/07/12/the-10-commandments-for-writers-jared-c-wilson/">loving them as yourself</a>: write because of a desire to serve and enrich them. For me, this means working to make my writing clear, concise, and coherent in order to ease my reader’s effort and maximize what they get for it. I like reading things that are clear and rich with information and insight, and I want to give what I enjoy receiving. However, you may have different values. If so, work to imbue your post with your values.</p><h3>Step 3: Research</h3><p>It bears repeating:<em> your writing will never be clearer than your thinking.</em> If you recognize that you have an insufficient understanding to write about your topic, you will first need to research it. This may not always be the case. For instance, I recently revised the <a href="https://github.com/RoleModel/BestPractices">RoleModel Best Practices</a> around how we use git, and I already understood git well enough that I didn’t need to research anything. I did have to look up details sometimes, but that’s different. Don’t seek to memorize the details but to <em>understand </em>the concepts.</p><p>If you’re not sure whether you need to research, the next step will help you make that decision. You can always come back and research more.</p><p>As you research, I recommend keeping a file open with a list of your sources. For each source, include the title, author, and location, along with a summary of things you found noteworthy. Here are some example phrases that are common in my summaries:</p><ul><li>“His main point was…”</li><li>“She did a good job articulating the point that…”</li><li>“I didn’t know that…”</li><li>“I hadn’t considered before the perspective that…”</li><li>“I disagree with him that…”</li></ul><p>Later, read and consider your notes to more deeply digest the various resources you just consumed. Again, the point is to understand, and understanding doesn’t necessarily come by reading things, nor even by writing summaries about them. <em>Ruminate</em> about what you read. The word ‘ruminate’ technically means chew the cud, which is to say, bring up the half-digested stuff and chew on it some more in order to digest it more thoroughly. I find this an apt metaphor for the process of understanding something, as you bring back to mind and ‘re-chew’ ideas until they’re ‘digested’ into your understanding.</p><h3>Step 4: Braindump</h3><p>Braindumping is the secret weapon in my writing toolbox. Take everything you know about your topic and get all of it into your editor. It probably won’t be clear or coherent. It probably will be meandering. Just get it all out there.</p><p>Why is this useful? Many people get stuck when they try to write because they’re trying to write a perfect post on their first attempt. Braindumping is a way of dividing the work. Once all the content is out there, then you can organize it. Being able to ignore organization is enormously helpful in overcoming writer’s block.</p><p>How does one braindump? First, remember your audience. Write to them in a casual way. Imagine that your target person walked up and said, “Tell me everything you know about this topic.” All you’re trying to do is capture your response in written form. If you have an idea about something, but you’re not sure about it, type it out the same way you’d tell your friend: “I’m not sure, but I think the way it works is…” If you realize as you type that something you said earlier was wrong or incomplete, don’t go back and revise; rather, just type out what you’d actually say in person: “Oh yeah, when I said that one thing, I just realized I should also say that…”</p><p>It’s essential to have faith in your ability to organize this content into something coherent later; otherwise, you’ll distract yourself from the braindumping process as you worry about organization. I suspect you’ll be surprised how well your writing cleans up, just like Tom Hanks’s character after he gets a haircut in <em>Castaway</em>.</p><p>Sometimes, as you braindump, you’ll notice that there is an area that’s harder to write about. Look out for this, because it means you may not understand that part very well yet. Get to a good stopping point in your braindumping, then research the issue, make sure you understand it, and come back to braindump what you’ve learned.</p><p>But isn’t this just a waste of time? Is this step really necessary? Well, no. It isn’t. But try it out and see if it works for you. If you’re like me, you might be pleasantly surprised how helpful it can be to get started and keep you moving in your writing.</p><h3>Step 5: Outline</h3><p>Once you’ve braindumped, go through what you’ve written and pick out the main points. Organize them into topics and form an outline. The idea here is to create a skeleton for what’s currently a rather lumpy pile of thoughts. Later, you’ll flesh it out into an actual draft, but for now, just the bones — the key ideas — will do.</p><p>Why is this useful? For the same reason as braindumping: outlining separates the organization process from the actual writing, so that the writing part is easy and you don’t get blocked. Divide and conquer.</p><p>While outlining, pay attention to how the main ideas relate. What ideas need to come before other ideas? Ordering things well is important to avoid confusing your readers, and outlining is the easiest time to do it.</p><p>Sometimes, some points don’t fit very well or seem to break up the flow. Pay attention when this happens. It might mean you need to rearrange your outline so that the missing points find a suitable home. Or it might mean that those points don’t really belong in this particular post. That’s OK. Save them for a follow-up post. Just don’t try to force a bad fit. You may end up losing your reader at that point as you wander away from your main topic.</p><h3>Step 6: Draft</h3><p>Now that we have an outline, the next step is to write a draft. Put some skin on the bones of the outline. I’ve been careful to make this step as tractable as possible by separating related concerns like braindumping and outlining into prerequisite steps. Similarly, if you have a good outline, you can write about each section of your outline without concern for the overall post. Also, we will have plenty of time for revising later, so just get your thoughts down. Again, the guiding principle here is <em>divide and conquer</em>.</p><p>Despite the relatively small tasks, I often struggle with this step. In fact, I rarely get stuck on any other step. Usually, my challenges are not technical so much as emotional. Here are some thoughts I’ve wrestled with most often:</p><ul><li>“<a href="https://www.youtube.com/watch?v=qm7S26x5U9s">Dang it</a>. This is hard.”</li><li>“This isn’t turning out nearly as awesome as I thought it would.”</li><li>“But what if I’m wrong about this?”</li></ul><p>I often start out thinking that writing will be easy and fast. When the words don’t flow effortlessly through my fingers to the page, or it’s taking <em>so much longer</em> than I expected, that can be discouraging. (For example, this post took me 15 hours, and I didn’t even need to do any research for it.) My approach here is just to keep moving. (Enabling steady progress is an important design principle for my writing process.) If the words aren’t flowing, try revisiting an earlier step to see if you can further simplify the process. Also, keep in mind that editing works wonders. I have a friend who revised her book 9 times, cover to cover, before it was finally published. Have faith in the power of editing.</p><p>I often make the mistake early in my writing process of dreaming about how excellent my post will be and how many people will read it and be amazed at my insight and general awesomeness. Although it can be fun to dream, this typically (at least for me) has two negative effects. First, the person I’m writing to gets lost in a sea of hypothetical readers. Losing that connection to a real person often makes it harder to know what to say or where to start. Second, riding the wave of the so-called <a href="https://en.wikipedia.org/wiki/Hype_cycle">Hype Cycle</a> lands me in the “trough of disillusionment,” where my dreams give way to despair that my writing is opaque, my ideas are trite, and nobody will enjoy it or be enriched by it.</p><p>I’ve identified three ways to counter these strong emotions. First, recognize the cycle, which helps to neutralize it, as you can actively temper your expectations. Second, reconnect with your audience by remembering the specific person you’ve chosen as part of the process. Third, define success. What results would you be content with for your post? When I stop to define success, my vague dreams of many viewers and retweets are exposed as evanescent. I tend towards a goal like: “I want to be proud of what I wrote, even if nobody else likes it.”</p><p>Lastly, I sometimes get stuck for fear of getting things wrong and looking foolish. This can be paralyzing! I’ve found three things helpful to keep in mind. First, I can always go back and research more if I discover that I don’t yet understand my topic sufficiently. Second, if I humbly mention my uncertainty, few people will be offended if I say the wrong thing. Lastly, if I discover later that I was wrong about something I wrote, I can write a follow-up post correcting myself. Have you ever read a post in which the author corrected themselves or changed their minds after learning something new? I suspect that most people receive this public self-correction with respect rather than scoffing. It’s OK to be wrong; just be humble.</p><h3>Step 7: Revise</h3><p>Once you’ve written a draft, it’s time to revise it. This step is perhaps the most important. If you invest enough energy into revising your post, you can help it be excellent, insightful, and compelling by noticing and correcting issues and tightening the expression of your ideas. Depending on the occasion, I might revise a post between one and five times, often soliciting feedback from trusted friends. This takes time, effort, and attention to detail, but the power of good revision to improve your work is considerable.</p><p>There are a couple of levels of revisions that you can make. One is proofreading: focusing on mechanics like spelling, grammar, and punctuation. If you’re not the person on your team that’s annoyingly attuned to these details, enlist that person to help.</p><p>To me, the harder thing to assess in a draft is the higher level of content. Here are some things I look for:</p><ul><li>Do the ideas flow well, with good transitions between them and a clear relationship to the main idea? Are the sections and paragraphs therein ordered well?</li><li>Is the content well motivated with a clear statement of the problem?</li><li>Have I captured readers’ attention?</li><li>Is there too little or too much detail?</li><li>Is all of the content relevant to the main idea?</li><li>Is the document skimmable? Are there noticeable section titles and paragraphs well-summarized by opening sentences and phrases?</li><li>Are there enough examples of abstract ideas or principles?</li><li>Is the writing consistent in tone, verb tense, and perspective?</li></ul><p>For me, these things require careful consideration. If I can, I try to read it with fresh eyes. If I can’t, I’ll do something else until the writing is out of mind. This often means waiting until the next day. Then, as I read from start to finish, I take note of anything that feels funny and come back to fix the issue afterward.</p><p>One mistake that I often make, especially when drafting, is being too abstract. Being abstract is a great way to kill a post through sheer boredom! The best solution I’ve found is to add concrete examples or illustrations that people can relate to. It’s worth noting, though, that there is a tension between ‘color’ and concision.</p><p>Once I have a decent draft, I’ll let others read it. It’s hard to see your own blind spots, but often others will immediately notice them. You don’t have to incorporate every suggestion, but it’s valuable to understand not just the content of the suggestion, but also <em>why</em> your reader suggested what she did. There may be a different perspective there that could enrich your post. How often have you read a post and thought, “But they just don’t get this crucial point!” Your initial readers might provide a thread for you to follow that will help you acknowledge readers who have a different perspective so that they don’t feel alienated and close their browser tab in disgust.</p><h3>Conclusion</h3><p>Writing is hard. But by separating the writing process into different steps, such as braindumping and outlining, you can break down an unwieldy and intimidating task into smaller, individually tractable ones. I hope that reading about my approach will equip you to tackle your next writing project.</p><h3>Acknowledgements</h3><p>Thanks to my wife Emily, my friend David Ferrell, and my colleague Gregg Shupe for reading drafts and providing excellent feedback and suggestions.</p><p><em>What do you think? I’m interested to hear about your experience, especially if you disagree with this approach or if you try it yourself. Please leave a comment below.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed58edcdc17c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rolemodel-software/how-to-write-a-blog-post-ed58edcdc17c">The divide-and-conquer strategy applied to writing blog posts</a> was originally published in <a href="https://medium.com/rolemodel-software">RoleModel Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>