91 lines
No EOL
2.8 KiB
JSON
91 lines
No EOL
2.8 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "bbbe114e-124b-40cb-a884-9edd94353bba"
|
|
}
|
|
],
|
|
"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:30+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": "Some solutions are good enough\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-10-05T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:30+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2023\/10\/05\/some-solutions-are-good-enough",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Once you have a passing test and you're confident your code works as expected, what do you do next?<\/p>\n\n<p>Do you keep refactoring and changing it, or is it good enough?<\/p>\n\n<p>Do you need to extract additional classes and methods now, or as the test is passing, do you move on to the next task?<\/p>\n\n<p>The main objective is to ship the change and for it to provide value to users, not to have a perfect or \"gold-plated\" solution.<\/p>\n\n<p>Once it's shipped, because you have tests, you can confidently refactor it in the future.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Once you have a passing test and you're confident your code works as expected, what do you do next?<\/p>\n\n<p>Do you keep refactoring and changing it, or is it good enough?<\/p>\n\n<p>Do you need to extract additional classes and methods now, or as the test is passing, do you move on to the next task?<\/p>\n\n<p>The main objective is to ship the change and for it to provide value to users, not to have a perfect or \"gold-plated\" solution.<\/p>\n\n<p>Once it's shipped, because you have tests, you can confidently refactor it in the future.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |