uuid: - value: a8d650da-84f6-4d81-9384-bb26228f3dcb 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: 'Testing personal projects' created: - value: '2024-09-28T00: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/09/28/testing-personal-projects langcode: en body: - value: |
Listening to podcasts and watching videos where Developers talk about their personal or side projects, sometimes they say that they skip writing automated tests.
They'd write tests for their client or work projects, but not necessarily for their own projects.
I wonder why this is.
Presumably they see the benefits of testing on other projects, so why wouldn't they write tests for their own projects?
format: full_html processed: |Listening to podcasts and watching videos where Developers talk about their personal or side projects, sometimes they say that they skip writing automated tests.
They'd write tests for their client or work projects, but not necessarily for their own projects.
I wonder why this is.
Presumably they see the benefits of testing on other projects, so why wouldn't they write tests for their own projects?
summary: null field_daily_email_cta: { }