100 lines
No EOL
3.7 KiB
JSON
100 lines
No EOL
3.7 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "c8fd5532-9338-4ea0-933f-798ce5782931"
|
|
}
|
|
],
|
|
"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:07+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": "What's your plan?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-09-14T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:07+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/09\/14\/whats-your-plan",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>A question I ask before starting a task, whether I'm working solo or as part of a team is \"What is your plan?\".<\/p>\n\n<p>How am I going to approach the task I'm about to start working on?<\/p>\n\n<p>What information do I need?<\/p>\n\n<p>What approach am I going to take and which am I not going to take?<\/p>\n\n<p>What will some of the\u00a0puzzle pieces be? Will I need a route, a Controller, a Service, a Command, a Value Object?<\/p>\n\n<p>Asking these questions and making these initial decisions upfront greatly reduces my implementation time as I only need to focus on delivering what I've already planned.<\/p>\n\n<p>And I can <a href=\"\/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"\/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>A question I ask before starting a task, whether I'm working solo or as part of a team is \"What is your plan?\".<\/p>\n\n<p>How am I going to approach the task I'm about to start working on?<\/p>\n\n<p>What information do I need?<\/p>\n\n<p>What approach am I going to take and which am I not going to take?<\/p>\n\n<p>What will some of the puzzle pieces be? Will I need a route, a Controller, a Service, a Command, a Value Object?<\/p>\n\n<p>Asking these questions and making these initial decisions upfront greatly reduces my implementation time as I only need to focus on delivering what I've already planned.<\/p>\n\n<p>And I can <a href=\"http:\/\/default\/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"http:\/\/default\/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:32:50+00:00",
|
|
"guid": null,
|
|
"hash": "9c34aa974d9627eacb1aee7476f85467",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |