uuid:
  - value: a5a69bcd-a7f7-4957-ab0b-393437e4055d
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: |
      The contribution-first workflow
created:
  - value: '2023-12-01T00: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/01/the-contribution-first-workflow
    langcode: en
body:
  - value: |
      <p>I've worked on many software projects with a lot of custom code.</p>

      <p>Not all the code is specific to that client or project, and often, code is identified as it can be extracted from the project and open-sourced as a Drupal module, PHP or JavaScript library, or Tailwind CSS plugin.</p>

      <p>Usually, the code is written as custom code initially, with the best intentions to revisit it once the project is complete and open-source it.</p>

      <p>But this rarely happens, as there's always the next sprint or project waiting.</p>

      <p>It takes too long to extract the code as it usually needs to be tidied or refactored beforehand.</p>

      <p>It may have been written with the client or project name within the code, which needs changing.</p>

      <p>My suggestion is to avoid this step.</p>

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

      <p>Instead of writing it as custom code and hopefully extracting it later, start it as a separate module, library or plugin, and use Composer or npm to add it to your project as another dependency.</p>

      <p>Whilst it's a slightly smaller overhead, it's better and less risky than rewriting or refactoring code later and it's already open-sourced.</p>

      <p>Plus, you may get some issues, testing and improvements from others along the way.</p>

              
    format: full_html
    processed: |
      <p>I've worked on many software projects with a lot of custom code.</p>

      <p>Not all the code is specific to that client or project, and often, code is identified as it can be extracted from the project and open-sourced as a Drupal module, PHP or JavaScript library, or Tailwind CSS plugin.</p>

      <p>Usually, the code is written as custom code initially, with the best intentions to revisit it once the project is complete and open-source it.</p>

      <p>But this rarely happens, as there's always the next sprint or project waiting.</p>

      <p>It takes too long to extract the code as it usually needs to be tidied or refactored beforehand.</p>

      <p>It may have been written with the client or project name within the code, which needs changing.</p>

      <p>My suggestion is to avoid this step.</p>

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

      <p>Instead of writing it as custom code and hopefully extracting it later, start it as a separate module, library or plugin, and use Composer or npm to add it to your project as another dependency.</p>

      <p>Whilst it's a slightly smaller overhead, it's better and less risky than rewriting or refactoring code later and it's already open-sourced.</p>

      <p>Plus, you may get some issues, testing and improvements from others along the way.</p>

              
    summary: null
field_daily_email_cta: {  }