uuid: - value: eef4147e-e47a-411e-a7de-eb67638dc6bb 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: YAGNI created: - value: '2024-10-03T00: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/03/yagni langcode: en body: - value: |

I like to keep my code simple.

I only write the code I need to add the functionality I need, and I only include the current requirements.

There's no benefit to writing code for additional requirements that may never be needed or used.

I also think this when adding new modules or packages, or implementing a design pattern.

Do I really need this?

What value does it add?

Is there a simpler way to achieve the same thing?

If so, I'm happy to call YAGNI on it.

format: full_html processed: |

I like to keep my code simple.

I only write the code I need to add the functionality I need, and I only include the current requirements.

There's no benefit to writing code for additional requirements that may never be needed or used.

I also think this when adding new modules or packages, or implementing a design pattern.

Do I really need this?

What value does it add?

Is there a simpler way to achieve the same thing?

If so, I'm happy to call YAGNI on it.

summary: null field_daily_email_cta: { }