92 lines
3.5 KiB
YAML
92 lines
3.5 KiB
YAML
uuid:
|
|
- value: 0f349fae-6a04-42b4-979f-ed8428e97a2b
|
|
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:01+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: "Don't pre-optimise"
|
|
created:
|
|
- value: '2025-02-16T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:01+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/02/16/pre-optimise
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I recently had <a href="/podcast/27-drupalisms">my first podcast episode with two guests</a>, where I discussed Drupal terminology and Drupalisms with Emma Horrell and Luke McCormick.</p>
|
|
|
|
<p>It was a great episode, but there was something I needed to do before I could release it.</p>
|
|
|
|
<p>Before I could release the episode, I needed to update my website to show both guest names.</p>
|
|
|
|
<p>The other 26 episodes only had a single guest per episode, and my podcast pages were built to only show the first guest name.</p>
|
|
|
|
<p>When building the pages for the <a href="/podcast/1-retrofit">first episode with Matt Glaman</a>, I only needed to show a single guest name.</p>
|
|
|
|
<p>There was no need to show multiple guest names until I had an episode with multiple guests.</p>
|
|
|
|
<p>I wrote the simplest code to achieve the requirements I had at the time.</p>
|
|
|
|
<p>If I wrote for two guests but never had an episode with two guests, my website would be bloated and have functionality that wasn't needed or used.</p>
|
|
|
|
<p>Now my requirements have changed.</p>
|
|
|
|
<p>I can have an episode with one or two guests, but not three or more guests.</p>
|
|
|
|
<p>If I have an episode with more than two guests, I'll write that functionality then.</p>
|
|
|
|
<p>But not before.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I recently had <a href="/podcast/27-drupalisms">my first podcast episode with two guests</a>, where I discussed Drupal terminology and Drupalisms with Emma Horrell and Luke McCormick.</p>
|
|
|
|
<p>It was a great episode, but there was something I needed to do before I could release it.</p>
|
|
|
|
<p>Before I could release the episode, I needed to update my website to show both guest names.</p>
|
|
|
|
<p>The other 26 episodes only had a single guest per episode, and my podcast pages were built to only show the first guest name.</p>
|
|
|
|
<p>When building the pages for the <a href="/podcast/1-retrofit">first episode with Matt Glaman</a>, I only needed to show a single guest name.</p>
|
|
|
|
<p>There was no need to show multiple guest names until I had an episode with multiple guests.</p>
|
|
|
|
<p>I wrote the simplest code to achieve the requirements I had at the time.</p>
|
|
|
|
<p>If I wrote for two guests but never had an episode with two guests, my website would be bloated and have functionality that wasn't needed or used.</p>
|
|
|
|
<p>Now my requirements have changed.</p>
|
|
|
|
<p>I can have an episode with one or two guests, but not three or more guests.</p>
|
|
|
|
<p>If I have an episode with more than two guests, I'll write that functionality then.</p>
|
|
|
|
<p>But not before.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|