uuid:
  - value: efe699bf-ef82-4ce5-b87c-1cbb2e0aa420
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: |
      Test to save your job
created:
  - value: '2023-09-24T00: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/09/24/test-to-save-your-job
    langcode: en
body:
  - value: |
      <p>I've recently been going through my YouTube "Watch Later" list and watching (or rewatching) videos of conference and meetup talks that I saved to watch later.</p>

      <p>Today's talk was by Matt Stauffer at one of the previous Laracon conferences.</p>

      <p>I've quoted Matt previously when explaining what to test on applications. The answer: "The thing you'd lose your job for if it broke".</p>

      <p>In this talk, Matt has a slide that goes further into this, titled "Test to save your job".</p>

      <h2 id="what-matt-said">What Matt said</h2>

      <p>The best place to start your tests is by asking yourself: "What part of this app, if broken, would make me worried for my job?"</p>

      <ul>
      <li>What's most likely to break?</li>
      <li>What do I have the least control over?</li>
      <li>What are we about to refactor?</li>
      <li>What would make my clients stress out?</li>
      <li>What would make me stressed out?</li>
      </ul>

      <h2 id="what-about-you%3F">What about you?</h2>

      <p>Do you have any other ways to decide what code to test? Reply and let me know, as I'd love to know.</p>

              
    format: full_html
    processed: |
      <p>I've recently been going through my YouTube "Watch Later" list and watching (or rewatching) videos of conference and meetup talks that I saved to watch later.</p>

      <p>Today's talk was by Matt Stauffer at one of the previous Laracon conferences.</p>

      <p>I've quoted Matt previously when explaining what to test on applications. The answer: "The thing you'd lose your job for if it broke".</p>

      <p>In this talk, Matt has a slide that goes further into this, titled "Test to save your job".</p>

      <h2 id="what-matt-said">What Matt said</h2>

      <p>The best place to start your tests is by asking yourself: "What part of this app, if broken, would make me worried for my job?"</p>

      <ul>
      <li>What's most likely to break?</li>
      <li>What do I have the least control over?</li>
      <li>What are we about to refactor?</li>
      <li>What would make my clients stress out?</li>
      <li>What would make me stressed out?</li>
      </ul>

      <h2 id="what-about-you%3F">What about you?</h2>

      <p>Do you have any other ways to decide what code to test? Reply and let me know, as I'd love to know.</p>

              
    summary: null
field_daily_email_cta: {  }