uuid:
  - value: 162509c1-9ef9-4647-9ae5-843e6b214cce
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:34+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: |
      Don't estimate separately for testing
created:
  - value: '2023-08-13T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:34+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/08/13/dont-estimate-separately-for-testing
    langcode: en
body:
  - value: |
      <p>A common issue I see for people introducing automated testing is estimating the testing and implementation of a task separately.</p>

      <p>Something like, "It'll take x to do the work and x to write the tests for it".</p>

      <p>As well as implying you'd write all the code and then all the tests or vice versa, if you provide separate estimates, it's easy for someone to think the tests are optional and can be removed.</p>

      <p>If you provide one estimate for both, this can't happen.</p>

              
    format: full_html
    processed: |
      <p>A common issue I see for people introducing automated testing is estimating the testing and implementation of a task separately.</p>

      <p>Something like, "It'll take x to do the work and x to write the tests for it".</p>

      <p>As well as implying you'd write all the code and then all the tests or vice versa, if you provide separate estimates, it's easy for someone to think the tests are optional and can be removed.</p>

      <p>If you provide one estimate for both, this can't happen.</p>

              
    summary: null
field_daily_email_cta: {  }