91 lines
No EOL
3 KiB
JSON
91 lines
No EOL
3 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6"
|
|
}
|
|
],
|
|
"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": "Pair and mob programming are continuous code review\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-08-28T00: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\/28\/pair-and-mob-programming-are-continuous-code-review",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Instead of a single Developer working individually on a task and submitting it for a code review once complete, try pair or mob programming.<\/p>\n\n<p>As well as extra benefits, such as knowledge sharing and shared responsibility for the code, it's continuously reviewed and improved during the session.<\/p>\n\n<p>Questions from \"Why are we doing it this way?\" to \"What's the best name for this variable?\" can be asked, and decisions and changes can be made in real time.<\/p>\n\n<p>So, why wait until the task is complete and the code is harder to change to review it?<\/p>\n\n<p>Why not have it reviewed as it's written?<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Instead of a single Developer working individually on a task and submitting it for a code review once complete, try pair or mob programming.<\/p>\n\n<p>As well as extra benefits, such as knowledge sharing and shared responsibility for the code, it's continuously reviewed and improved during the session.<\/p>\n\n<p>Questions from \"Why are we doing it this way?\" to \"What's the best name for this variable?\" can be asked, and decisions and changes can be made in real time.<\/p>\n\n<p>So, why wait until the task is complete and the code is harder to change to review it?<\/p>\n\n<p>Why not have it reviewed as it's written?<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |