Move all files to tome/
This commit is contained in:
parent
5675bcfc36
commit
674daab35b
2874 changed files with 0 additions and 0 deletions
88
tome/content/node.0610a25f-884a-48b6-8be0-e969749d316a.yml
Normal file
88
tome/content/node.0610a25f-884a-48b6-8be0-e969749d316a.yml
Normal file
|
@ -0,0 +1,88 @@
|
|||
uuid:
|
||||
- value: 0610a25f-884a-48b6-8be0-e969749d316a
|
||||
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:02+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: 'Is it the application or implementation?'
|
||||
created:
|
||||
- value: '2025-01-28T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:02+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2025/01/28/application-or-implementation
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>With most things, it's easy to see where an issue is. There's only one way to build a car or a mobile phone, for example.</p>
|
||||
|
||||
<p>With other things, such as software, it's not as clear.</p>
|
||||
|
||||
<p>There are usually multiple ways to achieve the same result, but not all implementations are equal.</p>
|
||||
|
||||
<p>It's important to understand if an issue is caused by the software itself or how it's been implemented.</p>
|
||||
|
||||
<p>Some approaches may be quicker, better for end-user experience or more performant.</p>
|
||||
|
||||
<p>Each has its own advantages and disadvantages.</p>
|
||||
|
||||
<p>What was the correct solution then may not be the best one now.</p>
|
||||
|
||||
<p>Priorities may have changed or new approaches could be available.</p>
|
||||
|
||||
<p>You know more now about the problem that's being solved than you did at the time.</p>
|
||||
|
||||
<p>One of the original discarded solutions could now be the best option, or a new option that wasn't previously available that solves the problem in a different way.</p>
|
||||
|
||||
<p>The software may be capable of achieving what you want - it may just need to be configured in a different way.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>With most things, it's easy to see where an issue is. There's only one way to build a car or a mobile phone, for example.</p>
|
||||
|
||||
<p>With other things, such as software, it's not as clear.</p>
|
||||
|
||||
<p>There are usually multiple ways to achieve the same result, but not all implementations are equal.</p>
|
||||
|
||||
<p>It's important to understand if an issue is caused by the software itself or how it's been implemented.</p>
|
||||
|
||||
<p>Some approaches may be quicker, better for end-user experience or more performant.</p>
|
||||
|
||||
<p>Each has its own advantages and disadvantages.</p>
|
||||
|
||||
<p>What was the correct solution then may not be the best one now.</p>
|
||||
|
||||
<p>Priorities may have changed or new approaches could be available.</p>
|
||||
|
||||
<p>You know more now about the problem that's being solved than you did at the time.</p>
|
||||
|
||||
<p>One of the original discarded solutions could now be the best option, or a new option that wasn't previously available that solves the problem in a different way.</p>
|
||||
|
||||
<p>The software may be capable of achieving what you want - it may just need to be configured in a different way.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue