100 lines
No EOL
4.3 KiB
JSON
100 lines
No EOL
4.3 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "63cd9b17-a81d-49aa-9f30-ebff14a96440"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:12:56+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": "Don't over rely on AI"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-01-12T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:56+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/01\/12\/reliance",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I've occasionally been experimenting with AI whilst programming.<\/p>\n\n<p>Not in my editor, but asking it questions if I'm unsure how to do something or something isn't working.<\/p>\n\n<p>As a pair programming partner of sorts.<\/p>\n\n<p>Its results and suggestions are still mixed.<\/p>\n\n<p>But I've noticed I've started to ask AI for answers to simple questions I can find or figure out myself.<\/p>\n\n<p>Things like how to show more verbose output for a command, which I can find from the command's help text or manual.<\/p>\n\n<p>This was part of a larger issue which, instead of asking AI, I would usually investigate by reading the available documentation or source code.<\/p>\n\n<p>I don't want to lose my problem solving skills.<\/p>\n\n<p>I like reading documentation and code to learn more about the tools I'm using and to solve issues I encounter.<\/p>\n\n<p>I like to read articles others have written on their websites about the same or similar issues.<\/p>\n\n<p>Whilst AI can be a useful tool, I don't want to become over reliant on it.<\/p>\n\n<p>I still want to be able to investigate, solve and learn things for myself and enjoy the process.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I've occasionally been experimenting with AI whilst programming.<\/p>\n\n<p>Not in my editor, but asking it questions if I'm unsure how to do something or something isn't working.<\/p>\n\n<p>As a pair programming partner of sorts.<\/p>\n\n<p>Its results and suggestions are still mixed.<\/p>\n\n<p>But I've noticed I've started to ask AI for answers to simple questions I can find or figure out myself.<\/p>\n\n<p>Things like how to show more verbose output for a command, which I can find from the command's help text or manual.<\/p>\n\n<p>This was part of a larger issue which, instead of asking AI, I would usually investigate by reading the available documentation or source code.<\/p>\n\n<p>I don't want to lose my problem solving skills.<\/p>\n\n<p>I like reading documentation and code to learn more about the tools I'm using and to solve issues I encounter.<\/p>\n\n<p>I like to read articles others have written on their websites about the same or similar issues.<\/p>\n\n<p>Whilst AI can be a useful tool, I don't want to become over reliant on it.<\/p>\n\n<p>I still want to be able to investigate, solve and learn things for myself and enjoy the process.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:56+00:00",
|
|
"guid": null,
|
|
"hash": "6e42e4070398b24d913cecbd7fa25945",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |