100 lines
No EOL
3.5 KiB
JSON
100 lines
No EOL
3.5 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "125a106e-aabb-4425-a72f-95bf6cf968b1"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T06:09:49+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": "TDD doesn't mean you know everything upfront"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-01-30T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T06:09:49+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/01\/30\/tdd-doesnt-mean-you-know-everything-upfront",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I'm in the final phase of a Drupal development project for a customer.<\/p>\n\n<p>It has some custom modules and code I wrote with automated tests and test-driven development.<\/p>\n\n<p>Today, the client reported a bug.<\/p>\n\n<p>But, instead of something working incorrectly, this was a use case I hadn't considered.<\/p>\n\n<p>The tests were passing, but there wasn't one for this.<\/p>\n\n<p>I wrote the code for the use cases I was aware of when I started, and now I'm aware of another, I can add a test for it and ensure it's tested and working.<\/p>\n\n<p>To do test-driven development, you don't need to know all the use cases and functionality upfront.<\/p>\n\n<p>Write for what you know at the time, then expand and iterate in the future.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I'm in the final phase of a Drupal development project for a customer.<\/p>\n\n<p>It has some custom modules and code I wrote with automated tests and test-driven development.<\/p>\n\n<p>Today, the client reported a bug.<\/p>\n\n<p>But, instead of something working incorrectly, this was a use case I hadn't considered.<\/p>\n\n<p>The tests were passing, but there wasn't one for this.<\/p>\n\n<p>I wrote the code for the use cases I was aware of when I started, and now I'm aware of another, I can add a test for it and ensure it's tested and working.<\/p>\n\n<p>To do test-driven development, you don't need to know all the use cases and functionality upfront.<\/p>\n\n<p>Write for what you know at the time, then expand and iterate in the future.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-05-11T06:09:49+00:00",
|
|
"guid": null,
|
|
"hash": "15b5f4507ca4a5cb62249ea0461feb8a",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |