77 lines
2.8 KiB
YAML
77 lines
2.8 KiB
YAML
uuid:
|
|
- value: 3d777436-a3ab-4465-b3c2-63d7eb28b50d
|
|
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:26+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: |
|
|
Are bugs good for users?
|
|
created:
|
|
- value: '2023-11-30T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:26+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/11/30/are-bugs-good-for-users
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I recently listened to a podcast episode that was discussing if bugs are good for users.</p>
|
|
|
|
<p>It suggested that bugs allowed for engagement between you and the user.</p>
|
|
|
|
<p>If someone reports a bug, you can tell them when you've fixed it. This encourages communication, and the customer will feel more connected to the product.</p>
|
|
|
|
<p>While this may be true, I think that users would prefer applications that just work.</p>
|
|
|
|
<p>If your application has major bugs, they may just go elsewhere. Maybe they won't even report the issue to you.</p>
|
|
|
|
<p>Major bugs can damage your reputation with your users and potential customers, as well as affect potential sales.</p>
|
|
|
|
<p>If you can avoid them to begin with, that's what I'd suggest. That's what tools and processes such as automated testing, test-driven development and static analysis are for.</p>
|
|
|
|
<p>When a user reports it (if they do at all), it could be too late.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I recently listened to a podcast episode that was discussing if bugs are good for users.</p>
|
|
|
|
<p>It suggested that bugs allowed for engagement between you and the user.</p>
|
|
|
|
<p>If someone reports a bug, you can tell them when you've fixed it. This encourages communication, and the customer will feel more connected to the product.</p>
|
|
|
|
<p>While this may be true, I think that users would prefer applications that just work.</p>
|
|
|
|
<p>If your application has major bugs, they may just go elsewhere. Maybe they won't even report the issue to you.</p>
|
|
|
|
<p>Major bugs can damage your reputation with your users and potential customers, as well as affect potential sales.</p>
|
|
|
|
<p>If you can avoid them to begin with, that's what I'd suggest. That's what tools and processes such as automated testing, test-driven development and static analysis are for.</p>
|
|
|
|
<p>When a user reports it (if they do at all), it could be too late.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|