var __defProp = Object.defineProperty;
var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
var __getOwnPropNames = Object.getOwnPropertyNames;
var __hasOwnProp = Object.prototype.hasOwnProperty;
var __export = (target, all) => {
  for (var name in all)
    __defProp(target, name, { get: all[name], enumerable: true });
};
var __copyProps = (to, from, except, desc) => {
  if (from && typeof from === "object" || typeof from === "function") {
    for (let key of __getOwnPropNames(from))
      if (!__hasOwnProp.call(to, key) && key !== except)
        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
  }
  return to;
};
var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
var stdin_exports = {};
__export(stdin_exports, {
  default: () => _2020_10_24_writing_for_recipe_cards,
  metadata: () => metadata
});
module.exports = __toCommonJS(stdin_exports);
var import_index_10ac95e2 = require("./index-10ac95e2.js");
const metadata = {
  "title": "Tiny thought: Writing for recipe cards",
  "author": "Thomas Wilson",
  "date": "2020-10-24T00:00:00.000Z",
  "draft": false,
  "slug": "2020-10-24-writing-for-recipe-cards",
  "tags": ["tinythought", "essay", "writing"]
};
const _2020_10_24_writing_for_recipe_cards = (0, import_index_10ac95e2.c)(($$result, $$props, $$bindings, slots) => {
  return `<p><em>Tiny Thoughts</em> are little (500 word) essays. They\u2019re concise.</p>
<p>I\u2019ve spent the past three months consciously trying to write and read more. I want to improve my ability to refine and communicate thought, and doing it in public helps motivate me to produce work.</p>
<p>One of the hardest problems I find myself addressing frequently is my desire to over-explain or provide too much information. I have read many times that good writing is about being concise. Being direct and undistracted help you get your point across. You\u2019re not tiring the reader, and you\u2019re not brining in unnecessary information. Being concise is good.</p>
<p>A few weeks ago I was listening to the JS Party podcast, a show I subscribe to but often skip. I picked up this episode because its title, <em><a href="${"https://changelog.com/jsparty/141"}" rel="${"nofollow"}">Content is Queen</a></em>, seemed relevant. I don\u2019t see my writing as content, but I know other people view theirs that way - and so I listened it.</p>
<p>Something that came from that episode, which I really liked, was the idea that <strong>you should write like you\u2019re creating a small recipe card</strong>. It\u2019s a good analogy, and it implies the following things to think about when you\u2019re writing:</p>
<ol><li>Realise sometimes you\u2019re trying to get to a point or a result, you\u2019re not trying to be witty or identifiable in your writing style.</li>
<li>Identify and sign-post the most important steps in a process, or points in an argument.</li>
<li>Figure out how to your points reproducible, undeniably clear, and re-usable.</li>
<li>Condense your points down to as small a number as possible, you\u2019re writing for a small recipe card.</li></ol>
<p>I don\u2019t know how well these items hold for longer pieces, or opinion pieces. Sometimes you want to let your personality shine through in your writing, and sometimes you can let yourself wander. That said, I\u2019ve been working a lot harder on <em>deleting</em> sentences, rather than adding them in, for the past month or so. I think that\u2019s, at least in part, because of this little realisation.</p>
<p>You can see the full transcript for the episode on the<a href="${"https://changelog.com/jsparty/141"}" rel="${"nofollow"}">episode page</a>, but the original quote comes from <a href="${"https://www.stephaniemorillo.co/"}" rel="${"nofollow"}">Stephanie Morillo</a> that sent me on this thought is:</p>
<blockquote><p>You know the recipes you get with a Blue Apron or a Sun Basket subscription? They fit on a card, right? And they\u2019re not superfluous and they\u2019re not using all these great words. Every word there is there for a reason, and they\u2019re not gonna give you the back-story and all that fun stuff. They are \u201CYou\u2019ve gotta do this, you\u2019ve gotta do this, you\u2019ve gotta do this.\u201D But the great thing is that as a result, you pretty much don\u2019t mess up the recipe.</p></blockquote>`;
});