{ "uuid": [ { "value": "2234ff18-11e6-4689-9316-cae9fb3f0579" } ], "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:34+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": "Work in small chunks\n" } ], "created": [ { "value": "2023-08-26T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:34+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2023\/08\/26\/work-in-small-chunks", "langcode": "en" } ], "body": [ { "value": "\n

When working with teams who are starting with automated tests and test-driven development, a common issue is being stuck on a failing test and trying to do too much at once while getting it to pass.<\/p>\n\n

Instead, work in small bite-sized iterations and focus on getting the test to pass as quickly as possible.<\/p>\n\n

You don't want to be stuck in a failing state for longer than you need to.<\/p>\n\n

Run the tests often, write the simplest code possible and don't write any code that isn't driven by a failing test.<\/p>\n\n

Don't make too many changes at once so, if you do get stuck, you can reset to the last working test and start again.<\/p>\n\n ", "format": "full_html", "processed": "\n

When working with teams who are starting with automated tests and test-driven development, a common issue is being stuck on a failing test and trying to do too much at once while getting it to pass.<\/p>\n\n

Instead, work in small bite-sized iterations and focus on getting the test to pass as quickly as possible.<\/p>\n\n

You don't want to be stuck in a failing state for longer than you need to.<\/p>\n\n

Run the tests often, write the simplest code possible and don't write any code that isn't driven by a failing test.<\/p>\n\n

Don't make too many changes at once so, if you do get stuck, you can reset to the last working test and start again.<\/p>\n\n ", "summary": null } ] }