From d59ea54a37f0681cd242a9d9f52fcf0643d259a7 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Tue, 3 Jan 2023 10:55:35 +0000 Subject: [PATCH] docs(daily-email): add 2022-12-31 --- website/src/daily-emails/2022-12-31.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 website/src/daily-emails/2022-12-31.md diff --git a/website/src/daily-emails/2022-12-31.md b/website/src/daily-emails/2022-12-31.md new file mode 100644 index 000000000..bfff792a6 --- /dev/null +++ b/website/src/daily-emails/2022-12-31.md @@ -0,0 +1,23 @@ +--- +title: > + Just start writing +pubDate: 2022-12-31 +permalink: > + archive/2022/12/31/just-start-writing +tags: + - productivity +--- + +Whether it's writing code or a technical design document, diagnosing an issue, or working on a blog post or a presentation deck, sometimes, the hardest part for me is getting started. + +When this happens, I try to find the smallest thing I can do to start the task and get the ball rolling. + +This could be just opening Neovim or Notion and finding the smallest task I can do to get going. + +In code, it could be making the smallest change to start on the task or committing a small refactoring on another part of the code to get into the flow. + +With a technical design document, once I've written the first heading, "What problem are we trying to solve?" and started to describe the problem, it's easy to continue writing the rest of the document. + +For a blog post or presentation, I've found that writing the headings first is a good starting point, adds structure and makes it easier to add the main content. + +Things are great once the ball is rolling; the question sometimes is, "what is the simplest thing I can do to start it?".