{ "uuid": [ { "value": "38535020-c00e-4720-8534-73346ff7cb0d" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-19T23:42:43+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": "Learning lessons" } ], "created": [ { "value": "2025-05-19T22:12:40+00:00" } ], "changed": [ { "value": "2025-05-19T23:42:43+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2025\/05\/19\/learning-lessons", "langcode": "en" } ], "body": [ { "value": "

Once you've resolved an issue and restored service<\/a>, what lessons can be learned to ensure the same issue doesn't happen again?<\/p>

Could the issue have been caught or identified sooner, before it got to production?<\/p>

Ideally, an issue would be identified in a local environment, in a CI pipeline or a staging environment.<\/p>

Anything before production, but the sooner, the better.<\/p>

Can you introduce more tools or automated checks?<\/p>

PHP in particular has a lot of tools for linting, analysing and testing code, such as PHPStan and PHPUnit.<\/p>

These can be run locally or automatically within a CI pipeline.<\/p>

If the pipeline is passing, the code should be deployable.<\/p>

But, if there is an issue, what needs to be added to the pipeline that would have identified it?<\/p>

How can you iterate and make your development and deployment processes better and more robust?<\/p>", "format": "basic_html", "processed": "

Once you've resolved an issue and restored service<\/a>, what lessons can be learned to ensure the same issue doesn't happen again?<\/p>

Could the issue have been caught or identified sooner, before it got to production?<\/p>

Ideally, an issue would be identified in a local environment, in a CI pipeline or a staging environment.<\/p>

Anything before production, but the sooner, the better.<\/p>

Can you introduce more tools or automated checks?<\/p>

PHP in particular has a lot of tools for linting, analysing and testing code, such as PHPStan and PHPUnit.<\/p>

These can be run locally or automatically within a CI pipeline.<\/p>

If the pipeline is passing, the code should be deployable.<\/p>

But, if there is an issue, what needs to be added to the pipeline that would have identified it?<\/p>

How can you iterate and make your development and deployment processes better and more robust?<\/p>", "summary": "" } ] }