Remove the feeds module

content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've worked on many software projects with a lot of custom code.<\/p>\n\n<p>Not all the code is specific to that client or project, and often, code is identified as it can be extracted from the project and open-sourced as a Drupal module, PHP or JavaScript library, or Tailwind CSS plugin.<\/p>\n\n<p>Usually, the code is written as custom code initially, with the best intentions to revisit it once the project is complete and open-source it.<\/p>\n\n<p>But this rarely happens, as there's always the next sprint or project waiting.<\/p>\n\n<p>It takes too long to extract the code as it usually needs to be tidied or refactored beforehand.<\/p>\n\n<p>It may have been written with the client or project name within the code, which needs changing.<\/p>\n\n<p>My suggestion is to avoid this step.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of writing it as custom code and hopefully extracting it later, start it as a separate module, library or plugin, and use Composer or npm to add it to your project as another dependency.<\/p>\n\n<p>Whilst it's a slightly smaller overhead, it's better and less risky than rewriting or refactoring code later and it's already open-sourced.<\/p>\n\n<p>Plus, you may get some issues, testing and improvements from others along the way.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1489f86d52518013ecedf7b402c2c07e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }