uuid: - value: 168c59ab-cadd-4dfc-8c72-de82d6578885 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:06+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: 'Not all legacy code is technical debt' created: - value: '2024-10-01T00:00:00+00:00' changed: - value: '2025-05-11T09:00:06+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/10/01/not-all-legacy-code-is-technical-debt langcode: en body: - value: |

Technical debt is an overused term with people often referring to any legacy code, outdated dependencies or bugs as technical debt.

Technical debt specifically refers to the future cost when a short-term solution is selected over a more flexible or efficient one.

For example, hard-coding something for now and making it dynamic later.

It's not any code the current Developers didn't write or no longer want to support.

format: full_html processed: |

Technical debt is an overused term with people often referring to any legacy code, outdated dependencies or bugs as technical debt.

Technical debt specifically refers to the future cost when a short-term solution is selected over a more flexible or efficient one.

For example, hard-coding something for now and making it dynamic later.

It's not any code the current Developers didn't write or no longer want to support.

summary: null field_daily_email_cta: { }