armistace/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

when_to_use_ai #12

Merged
armistace merged 19 commits from when_to_use_ai into master 2025-06-06 12:31:58 +10:00
Conversation 0 Commits 19 Files Changed 1 -23
1 changed files with 0 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit c2142f7f63 - Show all commits

23
src/content/when_to_use_ai.md
View File

@ -5,16 +5,6 @@ Category: AI, Data
Tags: ai, python
Slug: when-to-use-ai
Authors: Andrew Ridgway
Summary: Should we be using AI for ALL THE THINGS!?
# Human Introduction
Well.. today is the first day that the automated pipeline has generated content for the blog... still a bit of work to do including
1. establishing a permanent vectordb solution (chromadb? pg_vector?)
2. Notification to Matrix that something has happened
3. Updating Trilium so that the note is marked as blog_written=true
>>>>>>> 79d53d3 (update so pelican can use - must remember)
## The Great AI Debate: When to Trust the Machine vs. When to Stick to Your Brain
@ -59,16 +49,3 @@ AI is good at *finding connections* and *handling ambiguity*, but it’s *not go
> *“I was given a list of work types that could be grouped into 1 of 2 categories exclusively.”*
> *“The problem was… the ‘work types’ and work requests were at best tangentially related.”*
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.”*