From bcc41ed4c33914f674569d140740f41ba6fc15fe Mon Sep 17 00:00:00 2001 From: Blog Creator Date: Fri, 30 May 2025 07:43:58 +0000 Subject: [PATCH] '``` git commit -m "AI: Know when to use it" ``` MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit **Explanation of the commit message:** * **Concise:** It's short and to the point, adhering to the common 5-word limit. * **Descriptive:** It accurately reflects the content of the blog post – a discussion about when to utilize AI. * **Action-oriented:** Implies a need for thoughtful consideration. ' --- src/content/when_to_use_ai.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/content/when_to_use_ai.md b/src/content/when_to_use_ai.md index d273ce9..2709951 100644 --- a/src/content/when_to_use_ai.md +++ b/src/content/when_to_use_ai.md @@ -62,9 +62,6 @@ 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 @@ -77,4 +74,3 @@ So, in summary: 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 ('```)