uuid:
  - value: e0d6060d-596b-460f-9cac-22ef16a947b6
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:30+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: |
      Is test-driven development difficult?
created:
  - value: '2023-10-08T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:30+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/10/08/is-test-driven-development-difficult
    langcode: en
body:
  - value: |
      <p>I recently read a post where the writer said automated testing, test-driven development, continuous integration, trunk-based development, etc, are difficult.</p>

      <p>I'm familiar with them and have been using them for some time, but I think trunk-based development is easier as there's only a single branch instead of many.</p>

      <p>Continuous integration is pulling everyone else's code at least once daily and pushing yours to ensure it doesn't conflict.</p>

      <p>Test-driven development is writing failing tests before any implementation code and refactoring once it passes.</p>

      <p>I don't think these are technically difficult, but they do require an open mind, a willingness to learn, evaluate and consider alternative approaches and, in some cases, change existing behaviour.</p>

      <p>Change can be the difficult part, not which brand you commit to, how often you push your code or when you write your tests.</p>

              
    format: full_html
    processed: |
      <p>I recently read a post where the writer said automated testing, test-driven development, continuous integration, trunk-based development, etc, are difficult.</p>

      <p>I'm familiar with them and have been using them for some time, but I think trunk-based development is easier as there's only a single branch instead of many.</p>

      <p>Continuous integration is&nbsp;pulling everyone else's code at least once daily and pushing yours to ensure it doesn't conflict.</p>

      <p>Test-driven development is writing failing tests before any implementation code and refactoring once it passes.</p>

      <p>I don't think these are technically difficult, but they do require an open mind, a willingness to learn, evaluate and consider alternative approaches and, in some cases, change existing behaviour.</p>

      <p>Change can be the difficult part, not which brand you commit to, how often you push your code or when you write your tests.</p>

              
    summary: null
field_daily_email_cta: {  }