uuid: - value: 26e4ff33-b5fd-47b4-926e-fc5b78677c88 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:07+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: 'Make it work, then make it good' created: - value: '2024-08-31T00:00:00+00:00' changed: - value: '2025-05-11T09:00:07+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/08/31/make-it-work-then-make-it-good langcode: en body: - value: |
Your first objective when writing software is to make it work by - any means necessary.
If you're doing test-driven development, you want to get a failing test to pass as quickly as possible.
You want to get your application into a working state, whether that's hard-coding some values, focusing on the happy path implementation, holding off on implementing design patterns, or something else - you just want the code to work, even if it's a "bad" solution.
Once it's working, you can refactor it into a good solution.
format: full_html processed: |Your first objective when writing software is to make it work by - any means necessary.
If you're doing test-driven development, you want to get a failing test to pass as quickly as possible.
You want to get your application into a working state, whether that's hard-coding some values, focusing on the happy path implementation, holding off on implementing design patterns, or something else - you just want the code to work, even if it's a "bad" solution.
Once it's working, you can refactor it into a good solution.
summary: null field_daily_email_cta: { }