uuid: - value: c4bece9a-e11b-43a8-861a-2a64a12e5a91 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:08+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: "There isn't just one way to do something" created: - value: '2024-07-22T00:00:00+00:00' changed: - value: '2025-05-11T09:00:08+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/07/22/there-isnt-just-one-way-to-do-something langcode: en body: - value: |

In software development, there are usually multiple ways to achieve the same result.

There is no one "right" answer.

You can make a website look the same if you write the CSS by hand or use a framework.

When writing backend code, you could use design patterns and follow good clean code practices or not.

How you approach a solution depends on your experience and perspective, but one approach isn't wrong when compared to another if they achieve the same result.

Here's the thing

This is why I like pair and mob programming.

Everyone involved can discuss, plan and contribute to a solution in real-time.

You're more likely to get a better and more thought-out and robust solution from the collective perspective and experience compared to working individually, with the added benefit that more than one person understands the solution if it needs to be extended or changed in the future.

format: full_html processed: |

In software development, there are usually multiple ways to achieve the same result.

There is no one "right" answer.

You can make a website look the same if you write the CSS by hand or use a framework.

When writing backend code, you could use design patterns and follow good clean code practices or not.

How you approach a solution depends on your experience and perspective, but one approach isn't wrong when compared to another if they achieve the same result.

Here's the thing

This is why I like pair and mob programming.

Everyone involved can discuss, plan and contribute to a solution in real-time.

You're more likely to get a better and more thought-out and robust solution from the collective perspective and experience compared to working individually, with the added benefit that more than one person understands the solution if it needs to be extended or changed in the future.

summary: null field_daily_email_cta: { }