100 lines
No EOL
3.9 KiB
JSON
100 lines
No EOL
3.9 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "7d33f5f0-3eea-4bbc-9565-0d03aa4c6976"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-21T01:21:19+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": "Simpler code doesn't mean less code"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-02-09T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-21T01:21:19+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/02\/09\/simpler",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Just because I consider some code to be simpler, that doesn't necessarily mean there's less code.<\/p>\n\n<p>It's possible to write a whole function or class on one line, but that doesn't mean it's simple to read or understand.<\/p>\n\n<p>The opposite is also true.<\/p>\n\n<p>I can extract business logic from Controller classes into different service classes, commands or actions.<\/p>\n\n<p>I can use data transfer objects (DTOs), value objects and Collection classes to give names and meanings to things instead of always using generic strings, arrays or objects.<\/p>\n\n<p>I can follow design patterns and implement Repositories, Decorators, Factories and Builders to better organise code and make it easier to use and update.<\/p>\n\n<p>I can write tests that act as examples and executable documentation for people to see how to use the code I've written.<\/p>\n\n<p>This can all make code easier to read, understand and use - even though there is more of it.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Just because I consider some code to be simpler, that doesn't necessarily mean there's less code.<\/p>\n\n<p>It's possible to write a whole function or class on one line, but that doesn't mean it's simple to read or understand.<\/p>\n\n<p>The opposite is also true.<\/p>\n\n<p>I can extract business logic from Controller classes into different service classes, commands or actions.<\/p>\n\n<p>I can use data transfer objects (DTOs), value objects and Collection classes to give names and meanings to things instead of always using generic strings, arrays or objects.<\/p>\n\n<p>I can follow design patterns and implement Repositories, Decorators, Factories and Builders to better organise code and make it easier to use and update.<\/p>\n\n<p>I can write tests that act as examples and executable documentation for people to see how to use the code I've written.<\/p>\n\n<p>This can all make code easier to read, understand and use - even though there is more of it.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-21T01:21:19+00:00",
|
|
"guid": null,
|
|
"hash": "e59143196c70adc39a01487205db060b",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |