From fc48d9a4fd1a9821c1c69fe72c9c4b922facb049 Mon Sep 17 00:00:00 2001 From: Blog Creator Date: Fri, 30 May 2025 07:18:43 +0000 Subject: [PATCH] '``` feat: Add blog post on AI usage scenarios ```' --- src/content/when_to_use_ai.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/content/when_to_use_ai.md b/src/content/when_to_use_ai.md index 68fc0f7..d273ce9 100644 --- a/src/content/when_to_use_ai.md +++ b/src/content/when_to_use_ai.md @@ -62,4 +62,19 @@ So, when is it time to say “AI, nope”? When the data is messy, the tasks are | Repetitive tasks | ✅ | AI handles math and logic | | Creative decisions | ❌ | AI lacks the ability to think creatively | +<<<<<<< HEAD In the end, AI is just another tool. Use it when it works, and don’t let it define your workflow. 😄 *And if you ever feel like AI is overstepping, remember: it’s just trying to be helpful. Sometimes it’s not the best choice. Sometimes it’s the only choice.* +======= +So I had to manually read each work type and map it to a work request. It was a *shudder-inducing* task. + +## The Final Thought + +So, in summary: + +* **AI is not the best choice** when you need precision, accuracy, or a human touch. +* **AI is the best choice** when you need to handle ambiguity, find connections, or automate repetitive tasks. + +And that’s why I’m a journalist, a developer, and a DevOps expert. I know when to trust the machine and when to rely on my brain. + +> *“When in doubt, just do it.”* +>>>>>>> 9c92d19 ('```)