uuid:
  - value: 0f327d3d-33ce-498a-9234-6c1fe9f51d6a
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:20+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: 'Do you really need it?'
created:
  - value: '2024-02-10T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:20+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/02/10/do-you-really-need-it
    langcode: en
body:
  - value: |
      <p>Before adding a new feature or change to a codebase, ask if it's really needed and consider its long-term implications.</p>

      <p>Code is easy to write, but needs to be maintained as newer language or framework features are added or have breaking changes.</p>

      <p>Something I've added recently to Build Configs was an option to use an <a href="/daily/2024/01/27/gitignore-inclusive-or-exclusive">inclusive or exclusive .gitignore file</a>.</p>

      <p>Whilst it's only adding an if condition based on a value, it adds a separate path in my code and both need to be maintained.</p>

      <p>I've been thinking of adding <code>just</code> again to some projects instead of a <code>run</code> file, which would add separate files that need to be maintained and kept up-to-date with each other so both offer the same features.</p>

      <p>Is this something I want to maintain going forward? Does it add enough value to justify its maintenance?</p>

      <p>Different to a feature flag, which usually has a known lifespan, this could need be maintained for the whole lifespan of the application.</p>

      <p>On a client project, this could be having two sets of buttons with rounded and square corners.</p>

      <p>Do we need both?</p>

      <p>It could be the positioning of a title in a header. Fewer options mean there is less code to write and maintain.</p>

      <p>In a Drupal project, each choice could mean adding a different field, taxonomy term, or content or block type to achieve the desired result.</p>

      <p>The more we can achieve with fewer options means the application will be easier to maintain and work on in the future.</p>

              
    format: full_html
    processed: |
      <p>Before adding a new feature or change to a codebase, ask if it's really needed and consider its long-term implications.</p>

      <p>Code is easy to write, but needs to be maintained as newer language or framework features are added or have breaking changes.</p>

      <p>Something I've added recently to Build Configs was an option to use an <a href="http://default/daily/2024/01/27/gitignore-inclusive-or-exclusive">inclusive or exclusive .gitignore file</a>.</p>

      <p>Whilst it's only adding an if condition based on a value, it adds a separate path in my code and both need to be maintained.</p>

      <p>I've been thinking of adding <code>just</code> again to some projects instead of a <code>run</code> file, which would add separate files that need to be maintained and kept up-to-date with each other so both offer the same features.</p>

      <p>Is this something I want to maintain going forward? Does it add enough value to justify its maintenance?</p>

      <p>Different to a feature flag, which usually has a known lifespan, this could need be maintained for the whole lifespan of the application.</p>

      <p>On a client project, this could be having two sets of buttons with rounded and square corners.</p>

      <p>Do we need both?</p>

      <p>It could be the positioning of a title in a header. Fewer options mean there is less code to write and maintain.</p>

      <p>In a Drupal project, each choice could mean adding a different field, taxonomy term, or content or block type to achieve the desired result.</p>

      <p>The more we can achieve with fewer options means the application will be easier to maintain and work on in the future.</p>

              
    summary: null
field_daily_email_cta: {  }