92 lines
3.8 KiB
YAML
92 lines
3.8 KiB
YAML
uuid:
|
|
- value: 9deec245-c96a-44f5-a54c-95f61611051d
|
|
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:03+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: 'Working iteratively'
|
|
created:
|
|
- value: '2024-12-19T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:03+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/12/19/working-iteratively
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I recently started <a href="/daily/2024/12/18/self-hosting-podcast">self-hosting the episodes for the Beyond Blocks podcast</a>.</p>
|
|
|
|
<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.</p>
|
|
|
|
<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.</p>
|
|
|
|
<p>The second iteration was to change the player on the episode page.</p>
|
|
|
|
<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.</p>
|
|
|
|
<p>Each was its own deployable step, and this is how I like to approach tasks.</p>
|
|
|
|
<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.</p>
|
|
|
|
<p>Deploying features iteratively is less risky that deploying everything at once.</p>
|
|
|
|
<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.</p>
|
|
|
|
<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I recently started <a href="/daily/2024/12/18/self-hosting-podcast">self-hosting the episodes for the Beyond Blocks podcast</a>.</p>
|
|
|
|
<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.</p>
|
|
|
|
<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.</p>
|
|
|
|
<p>The second iteration was to change the player on the episode page.</p>
|
|
|
|
<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.</p>
|
|
|
|
<p>Each was its own deployable step, and this is how I like to approach tasks.</p>
|
|
|
|
<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.</p>
|
|
|
|
<p>Deploying features iteratively is less risky that deploying everything at once.</p>
|
|
|
|
<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.</p>
|
|
|
|
<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|