92 lines
No EOL
3 KiB
JSON
92 lines
No EOL
3 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "0d970bea-36e2-4f0c-b448-4be60af220ef"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-06-12T23:14:50+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": "Refactoring is a rabbit hole"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-06-12T23:00:07+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-06-12T23:14:50+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "",
|
|
"pid": null,
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "I enjoy refactoring code.\r\n\r\nOnce I've finished writing some code and all the tests are passing, I like reviewing what I've written and looking for ways to make it more readable or easier to maintain whilst making sure it still works.\r\n\r\nI usually start with one small refactor.\r\n\r\nThen I spot another.\r\n\r\nAnd another.\r\n\r\nI end up going down a refactoring rabbit hole and I keep seeing changes I could make.\r\n\r\nBut, at some point, you need to say enough refactoring and decide if the code is good enough to release, whether you do this yourself or as part of a pair or mob.\r\n\r\nIt can always be refactored more in the future, if needed.",
|
|
"format": "markdown",
|
|
"processed": "<p>I enjoy refactoring code.<\/p>\n<p>Once I've finished writing some code and all the tests are passing, I like reviewing what I've written and looking for ways to make it more readable or easier to maintain whilst making sure it still works.<\/p>\n<p>I usually start with one small refactor.<\/p>\n<p>Then I spot another.<\/p>\n<p>And another.<\/p>\n<p>I end up going down a refactoring rabbit hole and I keep seeing changes I could make.<\/p>\n<p>But, at some point, you need to say enough refactoring and decide if the code is good enough to release, whether you do this yourself or as part of a pair or mob.<\/p>\n<p>It can always be refactored more in the future, if needed.<\/p>\n",
|
|
"summary": ""
|
|
}
|
|
]
|
|
} |