100 lines
No EOL
3.4 KiB
JSON
100 lines
No EOL
3.4 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "4fdd7824-d2ef-4a4f-a6ca-80a5098af105"
|
|
}
|
|
],
|
|
"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:12+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": "Ask questions"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-05-30T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:12+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/05\/30\/ask-questions",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>As a Software Developer, it's common to hear that you need to ask questions to progress or work efficiently.<\/p>\n\n<p>You shouldn't just ask technical questions, though.<\/p>\n\n<p>Also ask questions like:<\/p>\n\n<ul>\n<li>What do we want to achieve by delivering this feature?<\/li>\n<li>How do we know if it's a success (or not)?<\/li>\n<li>What business value does this add and who will benefit?<\/li>\n<li>Why do this now? Why not wait a few months or not do it at all?<\/li>\n<li>Is there an existing solution for this?<\/li>\n<li>Can we achieve the same or a similar result in a different way?<\/li>\n<\/ul>\n\n<p>As well as knowing how to do something, it's important to know why it needs to be done.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>As a Software Developer, it's common to hear that you need to ask questions to progress or work efficiently.<\/p>\n\n<p>You shouldn't just ask technical questions, though.<\/p>\n\n<p>Also ask questions like:<\/p>\n\n<ul>\n<li>What do we want to achieve by delivering this feature?<\/li>\n<li>How do we know if it's a success (or not)?<\/li>\n<li>What business value does this add and who will benefit?<\/li>\n<li>Why do this now? Why not wait a few months or not do it at all?<\/li>\n<li>Is there an existing solution for this?<\/li>\n<li>Can we achieve the same or a similar result in a different way?<\/li>\n<\/ul>\n\n<p>As well as knowing how to do something, it's important to know why it needs to be done.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:32:50+00:00",
|
|
"guid": null,
|
|
"hash": "f0c3d6e951782cfb763d893c57d2dced",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |