Summary

Process

FAQs

• What is a regular post?

  A regular post is between 800 and 1200 words. Long-form posts, typically above 1200 words, take more time and effort to craft. They are not covered by this package, but if you are interested in them, talk to me, and we'll reach an agreement.

• Could it be 2 posts a month? Or 8?

  Yes, let's talk.

• What if we decide to postpone rolling out a feature that we were going to discuss in a blog post?

  I recommend having a minimum of two posts ready at all times to replace the one that bites the dust.

• Do you do research and link to sources?

  I always do due research and have my posts fact-checked by experts in my client's company. How much linking to sources will be done in the final draft ultimately depends on you. I can be Wikipedia-pedantic if you like.

• How do you write release notes?

  A typical software release includes new features, improvements, and a number of fixes—some trivial and some critical. The trick is to know what to focus on exactly, what level of detail to stick with, and when to stop and list some things under "Misc changes". Step 1 is to compile the overall list of changes; I can extract that from 'git log'. Step 2 is to categorize and group the changes. Step 3 is to assign importance to each one, then write the copy and make illustrations. The first few times I will need some help setting feature priorities. Once I know my way around the product, I can do that myself.