uuid:
  - value: a8e2e580-5b20-451d-80ef-7ee19aea62ec
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: |
      Rebuild or iterate
created:
  - value: '2023-12-09T00: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/12/09/rebuild-or-iterate
    langcode: en
body:
  - value: |
      <p>As I said in <a href="/daily/2023/12/08/dont-just-rewrite">yesterday's email</a>, I'm discussing with a team how to implement their new website design.</p>

      <p>Their website has been live for a couple of years, and now they want to refresh its look and feel.</p>

      <p>The current theme includes a lot of technical debt and legacy code, such as using an older CSS framework and build tools that need unsupported versions of packages to compile it and generate the scripts and stylesheets.</p>

      <p>There are two ways they could approach this:</p>

      <p>They could continue to iterate on the current theme, making and releasing small changes to move forward in small steps and slowly repaying the technical debt.</p>

      <p>Alternatively, they could create a new theme from scratch.</p>

      <p>This would allow them to start with new build tools, a modern CSS framework and small and simple stylesheets.</p>

      <h2 id="here%27s-the-thing">Here's the thing</h2>

      <p>There are advantages and disadvantages to both approaches.</p>

      <p>Iterating on the original theme allows for continuous improvement, but it would take longer to remove the old frameworks and build tools - if that would be possible at all.</p>

      <p>Rebuilding and re-inventing would mean immediately avoiding the technical debt and legacy tools, but it comes with its own risks, and you'd need to wait until the whole theme was completed before it could be launched.</p>

      <p>There isn't a right and wrong answer, and it will depend on the thoughts and objectives of the team and business.</p>

              
    format: full_html
    processed: |
      <p>As I said in <a href="http://default/daily/2023/12/08/dont-just-rewrite">yesterday's email</a>, I'm discussing with a team how to implement their new website design.</p>

      <p>Their website has been live for a couple of years, and now they want to refresh its look and feel.</p>

      <p>The current theme includes a lot of technical debt and legacy code, such as using an older CSS framework and build tools that need unsupported versions of packages to compile it and generate the scripts and stylesheets.</p>

      <p>There are two ways they could approach this:</p>

      <p>They could continue to iterate on the current theme, making and releasing small changes to move forward in small steps and slowly repaying the technical debt.</p>

      <p>Alternatively, they could create a new theme from scratch.</p>

      <p>This would allow them to start with new build tools, a modern CSS framework and small and simple stylesheets.</p>

      <h2 id="here%27s-the-thing">Here's the thing</h2>

      <p>There are advantages and disadvantages to both approaches.</p>

      <p>Iterating on the original theme allows for continuous improvement, but it would take longer to remove the old frameworks and build tools - if that would be possible at all.</p>

      <p>Rebuilding and re-inventing would mean immediately avoiding the technical debt and legacy tools, but it comes with its own risks, and you'd need to wait until the whole theme was completed before it could be launched.</p>

      <p>There isn't a right and wrong answer, and it will depend on the thoughts and objectives of the team and business.</p>

              
    summary: null
field_daily_email_cta: {  }