92 lines
3.6 KiB
YAML
92 lines
3.6 KiB
YAML
uuid:
|
|
- value: b5b7cf41-fa32-4c63-a182-9b048c290f05
|
|
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:22+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: 'Code is a liability, not an asset'
|
|
created:
|
|
- value: '2024-01-14T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:22+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/01/14/code-is-a-liability-not-an-asset
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Something I mentioned during my <a href="/podcast/7-mike-karthauser-testing-legacy">podcast episode with Mike Karthauser</a> is a quote I saw recently:</p>
|
|
|
|
<blockquote>
|
|
<p>Code is a liability, not an asset.</p>
|
|
</blockquote>
|
|
|
|
<p>The more code you write, the more you have to maintain.</p>
|
|
|
|
<p>The more complex the code is, the harder it is to maintain.</p>
|
|
|
|
<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?</p>
|
|
|
|
<p>Both can give the same result.</p>
|
|
|
|
<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.</p>
|
|
|
|
<p>There isn't a correct answer.</p>
|
|
|
|
<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.</p>
|
|
|
|
<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.</p>
|
|
|
|
<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Something I mentioned during my <a href="http://default/podcast/7-mike-karthauser-testing-legacy">podcast episode with Mike Karthauser</a> is a quote I saw recently:</p>
|
|
|
|
<blockquote>
|
|
<p>Code is a liability, not an asset.</p>
|
|
</blockquote>
|
|
|
|
<p>The more code you write, the more you have to maintain.</p>
|
|
|
|
<p>The more complex the code is, the harder it is to maintain.</p>
|
|
|
|
<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?</p>
|
|
|
|
<p>Both can give the same result.</p>
|
|
|
|
<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.</p>
|
|
|
|
<p>There isn't a correct answer.</p>
|
|
|
|
<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.</p>
|
|
|
|
<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.</p>
|
|
|
|
<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|