uuid:
  - value: 112ace31-6c57-405a-8c91-a2a19364fa20
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: |
      There is no perfect solution
created:
  - value: '2023-10-03T00: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/03/there-is-no-perfect-solution
    langcode: en
body:
  - value: |
      <p>Something I've said recently when mentoring bootcamp students and working with Junior Developers is that there isn't a perfect solution to each problem, and there are multiple ways to achieve the same result.</p>

      <p>Similarly, there isn't a perfect tool for every situation.</p>

      <p>You can use different tools and get the same outcome.</p>

      <p>In some of my early emails, I talked about <code>run</code> files and <code>just</code> - two ways to write project-specific commands or aliases that simplify complex commands or group multiple commands together.</p>

      <p>Both do the same thing, but each have pros and cons.</p>

      <p><code>run</code> files are files written in Bash, which are more verbose but can run anywhere.</p>

      <p>just is its own program that needs to be installed for it to be available, so Developers will need to have it installed, and it will need to be added to a CI pipeline to be available.</p>

      <p>I've had CI pipelines fail because they can't download just, and not because of anything in the application code.</p>

      <p>I like the simplicity of justfiles, though, and that the files are simpler.</p>

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

      <p>If there isn't a perfect solution, approach, or tool, it comes down to the pros and cons of each. Which option is best for you, your project, or your team?</p>

      <p>There isn't a "one size fits all" solution that works for everyone all the time.</p>

              
    format: full_html
    processed: |
      <p>Something I've said recently when mentoring bootcamp students and working with Junior Developers is that there isn't a perfect solution to each problem, and there are multiple ways to achieve the same result.</p>

      <p>Similarly, there isn't a perfect tool for every situation.</p>

      <p>You can use different tools and get the same outcome.</p>

      <p>In some of my early emails, I talked about <code>run</code> files and <code>just</code> - two ways to write project-specific commands or aliases that simplify complex commands or group multiple commands together.</p>

      <p>Both do the same thing, but each have pros and cons.</p>

      <p><code>run</code> files are files written in Bash, which are more verbose but can run anywhere.</p>

      <p>just is its own program that needs to be installed for it to be available, so Developers will need to have it installed, and it will need to be added to a CI pipeline to be available.</p>

      <p>I've had CI pipelines fail because they can't download just, and not because of anything in the application code.</p>

      <p>I like the simplicity of justfiles, though, and that the files are simpler.</p>

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

      <p>If there isn't a perfect solution, approach, or tool, it comes down to the pros and cons of each. Which option is best for you, your project, or your team?</p>

      <p>There isn't a "one size fits all" solution that works for everyone all the time.</p>

              
    summary: null
field_daily_email_cta: {  }