100 lines
No EOL
3 KiB
JSON
100 lines
No EOL
3 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "e1f231c9-ee99-485d-866a-25e24e716eeb"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:12:58+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": "YAGNI"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-10-03T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:58+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/10\/03\/yagni",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I like to keep my code simple.<\/p>\n\n<p>I only write the code I need to add the functionality I need, and I only include the current requirements.<\/p>\n\n<p>There's no benefit to writing code for additional requirements that may never be needed or used.<\/p>\n\n<p>I also think this when adding new modules or packages, or implementing a design pattern.<\/p>\n\n<p>Do I really need this?<\/p>\n\n<p>What value does it add?<\/p>\n\n<p>Is there a simpler way to achieve the same thing?<\/p>\n\n<p>If so, I'm happy to call YAGNI on it.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I like to keep my code simple.<\/p>\n\n<p>I only write the code I need to add the functionality I need, and I only include the current requirements.<\/p>\n\n<p>There's no benefit to writing code for additional requirements that may never be needed or used.<\/p>\n\n<p>I also think this when adding new modules or packages, or implementing a design pattern.<\/p>\n\n<p>Do I really need this?<\/p>\n\n<p>What value does it add?<\/p>\n\n<p>Is there a simpler way to achieve the same thing?<\/p>\n\n<p>If so, I'm happy to call YAGNI on it.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:58+00:00",
|
|
"guid": null,
|
|
"hash": "d55547f4588464a67252a7743560b0b3",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |