oliverdavies.uk/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.yml

73 lines
3.1 KiB
YAML

uuid:
- value: a986dbd9-92fb-45fc-9769-bf75542c9b49
langcode:
- value: en
type:
- target_id: daily_email
target_type: node_type
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
- value: '2025-05-11T09:00:50+00:00'
revision_uid:
- target_type: user
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: { }
status:
- value: true
uid:
- target_type: user
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
- value: |
Just start writing
created:
- value: '2022-12-31T00:00:00+00:00'
changed:
- value: '2025-05-11T09:00:50+00:00'
promote:
- value: false
sticky:
- value: false
default_langcode:
- value: true
revision_translation_affected:
- value: true
path:
- alias: /daily/2022/12/31/just-start-writing
langcode: en
body:
- value: |
<p>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.</p>
<p>When this happens, I try to find the smallest thing I can do to start the task and get the ball rolling.</p>
<p>This could be just opening Neovim or Notion and finding the smallest task I can do to get going.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Things are great once the ball is rolling; the question sometimes is, "what is the simplest thing I can do to start it?".</p>
format: full_html
processed: |
<p>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.</p>
<p>When this happens, I try to find the smallest thing I can do to start the task and get the ball rolling.</p>
<p>This could be just opening Neovim or Notion and finding the smallest task I can do to get going.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Things are great once the ball is rolling; the question sometimes is, "what is the simplest thing I can do to start it?".</p>
summary: null
field_daily_email_cta: { }