uuid:
  - value: 32313c89-b894-4ae7-b55d-a9bbd6af6dc6
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:38+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 any code without tests legacy code?
created:
  - value: '2023-06-26T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:38+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/06/26/is-any-code-without-tests-legacy
    langcode: en
body:
  - value: |
      <p>While I can't find the original quote, I've heard numerous people describe any code without automated tests as legacy.</p>

      <p>Legacy code is typically inherited from other Developers and is riskier to work on and harder to change, as there is no guarantee changing one piece of code won't cause breakages elsewhere in the codebase.</p>

      <p>This is true for code that doesn't have accompanying automated tests, regardless of when it was written.</p>

      <p>I can release a feature to an environment, and although it may be checked and tested at the time, it likely won't be again for every subsequent release. Automated tests can run automatically for every commit and before every deployment, ensuring the code continues to work and for it to be edited without causing regressions.</p>

              
    format: full_html
    processed: |
      <p>While I can't find the original quote, I've heard numerous people describe any code without automated tests as legacy.</p>

      <p>Legacy code is typically inherited from other Developers and is riskier to work on and harder to change, as there is no guarantee changing one piece of code won't cause breakages elsewhere in the codebase.</p>

      <p>This is true for code that doesn't have accompanying automated tests, regardless of when it was written.</p>

      <p>I can release a feature to an environment, and although it may be checked and tested at the time, it likely won't be again for every subsequent release. Automated tests can run automatically for every commit and before every deployment, ensuring the code continues to work and for it to be edited without causing regressions.</p>

              
    summary: null
field_daily_email_cta: {  }