91 lines
No EOL
3.1 KiB
JSON
91 lines
No EOL
3.1 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "c841583c-4e19-4eb2-898a-d7e61859daad"
|
|
}
|
|
],
|
|
"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:18+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": "Why write software for this?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-03-07T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:18+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/03\/07\/why-write-software-for-this",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Recently, when speaking with prospective clients, instead of focusing on the features they want, I like to ask questions like:<\/p>\n\n<p>What's wrong with what you have now?<\/p>\n\n<p>Why not fix what you have instead of rebuilding?<\/p>\n\n<p>What problem are you trying to solve?<\/p>\n\n<p>Why write software for this at all?<\/p>\n\n<p>Why not do it manually?<\/p>\n\n<p>Why do you need to do this now?<\/p>\n\n<p>What results would you expect to see after this project?<\/p>\n\n<p>If they can answer these types of questions and explain the business outcomes they're looking to achieve and what value I can add, those are the projects I want to work on.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Recently, when speaking with prospective clients, instead of focusing on the features they want, I like to ask questions like:<\/p>\n\n<p>What's wrong with what you have now?<\/p>\n\n<p>Why not fix what you have instead of rebuilding?<\/p>\n\n<p>What problem are you trying to solve?<\/p>\n\n<p>Why write software for this at all?<\/p>\n\n<p>Why not do it manually?<\/p>\n\n<p>Why do you need to do this now?<\/p>\n\n<p>What results would you expect to see after this project?<\/p>\n\n<p>If they can answer these types of questions and explain the business outcomes they're looking to achieve and what value I can add, those are the projects I want to work on.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |