Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
73
content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.yml
Normal file
73
content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.yml
Normal file
|
@ -0,0 +1,73 @@
|
|||
uuid:
|
||||
- value: 2facc6b4-52da-4fc5-b957-e29d06f19ae8
|
||||
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:32+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: |
|
||||
Do you proactively refactor your code?
|
||||
created:
|
||||
- value: '2023-09-08T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:32+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2023/09/08/do-you-proactively-refactor-your-code
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>Do you go back and proactively refactor code you've previously written?</p>
|
||||
|
||||
<p>In my experience, once some code is working, it's usually not reviewed again and refactored, and any TODO comments are still there.</p>
|
||||
|
||||
<p>If code is refactored, it's usually triggered by adding a new feature or fixing a bug that will be difficult or impossible with the existing code - i.e., make the change easy, then make the easy change.</p>
|
||||
|
||||
<p>Very rarely have I seen code be refactored to make it easier to read or change in the future.</p>
|
||||
|
||||
<p>Do you proactively refactor code or wait until something forces it to happen?</p>
|
||||
|
||||
<p>Do you not refactor code at all once it's been written?</p>
|
||||
|
||||
<p>Reply to this email and let me know which and why.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>Do you go back and proactively refactor code you've previously written?</p>
|
||||
|
||||
<p>In my experience, once some code is working, it's usually not reviewed again and refactored, and any TODO comments are still there.</p>
|
||||
|
||||
<p>If code is refactored, it's usually triggered by adding a new feature or fixing a bug that will be difficult or impossible with the existing code - i.e., make the change easy, then make the easy change.</p>
|
||||
|
||||
<p>Very rarely have I seen code be refactored to make it easier to read or change in the future.</p>
|
||||
|
||||
<p>Do you proactively refactor code or wait until something forces it to happen?</p>
|
||||
|
||||
<p>Do you not refactor code at all once it's been written?</p>
|
||||
|
||||
<p>Reply to this email and let me know which and why.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue