oliverdavies.uk/content/node.09073a81-2a1b-4200-905b-98b43152fe37.yml

65 lines
2.4 KiB
YAML

uuid:
- value: 09073a81-2a1b-4200-905b-98b43152fe37
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:26+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: |
Frequency reduces difficulty
created:
- value: '2023-11-22T00:00:00+00:00'
changed:
- value: '2025-05-11T09:00:26+00:00'
promote:
- value: false
sticky:
- value: false
default_langcode:
- value: true
revision_translation_affected:
- value: true
path:
- alias: /daily/2023/11/22/frequency-reduces-difficulty
langcode: en
body:
- value: |
<p>"Frequency reduces difficulty" is a phrase I heard on a podcast today, though I have heard it before.</p>
<p>It's a better way of saying, "If it hurts, do it more often".</p>
<p>If software deployments and releases are large, risky, and contain bugs, break them into smaller, less-risky deployments and release them more often.</p>
<p>If you get a lot of merge conflicts in Git, merge your code more frequently. Make your topic branches as short-lived as possible, or try trunk-based development and avoid topic branches by default.</p>
<p>If writing tests is difficult and takes time, persevere. It will get easier the more you do it, and you'll save time in the future by releasing fewer bugs and being able to refactor safely.</p>
format: full_html
processed: |
<p>"Frequency reduces difficulty" is a phrase I heard on a podcast today, though I have heard it before.</p>
<p>It's a better way of saying, "If it hurts, do it more often".</p>
<p>If software deployments and releases are large, risky, and contain bugs, break them into smaller, less-risky deployments and release them more often.</p>
<p>If you get a lot of merge conflicts in Git, merge your code more frequently. Make your topic branches as short-lived as possible, or try trunk-based development and avoid topic branches by default.</p>
<p>If writing tests is difficult and takes time, persevere. It will get easier the more you do it, and you'll save time in the future by releasing fewer bugs and being able to refactor safely.</p>
summary: null
field_daily_email_cta: { }