git commit -m "AI: Know when to use it"
```
**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.
'
git commit -m "AI: Know when to use it"
```
**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.
'
git commit -m "AI: Know when to use it"
```
**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.
'
git commit -m "AI: Know when to apply it"
```
**Explanation of the commit message:**
* **Concise:** It's short and to the point, fitting within the recommended 50-character limit.
* **Descriptive:** It accurately reflects the content's focus on appropriate AI usage.
* **Action-oriented:** "Know when to apply it" suggests a key takeaway for the reader.
'
When to use AI: Exploring Scenarios Where Human Expertise Still Shines Over LLMs 🚀
This commit refines the blog post on determining when artificial intelligence is appropriate, distinguishing between tasks where AI excels (text analysis, data patterns) and those requiring human precision (calculations, validation). The content emphasizes collaboration between AI and humans, using relatable examples like spreadsheet challenges and humorous analogies. Adjustments include clearer headings, concise paragraphs, and maintaining readability through short sentences. Humor is preserved to engage the audience effectively. 🚀✨
**Changes Made:**
- Updated "shudders" project explanation for clarity.
- Enhanced precision in AI limitations (mathematical accuracy vs. LLMs).
- Streamlined text interpretation triumph section with examples.
- Adjusted data cleaning conundrum to focus on preprocessing nuances.
- Finalized bottom line with actionable guidelines and closing humor.
**Next Steps:**
- Review for technical accuracy and ensure alignment with latest AI trends.
- Incorporate reader feedback from initial drafts into the final post.
- Optimize SEO keywords related to AI use cases for broader reach.
**Commit Notes:**
This commit aims to educate readers on practical AI adoption by highlighting both its strengths and limitations through relatable scenarios, fostering a balanced perspective on technology integration in professional settings. 🚀
<|end_of_solution|>'
This commit adds a detailed blog post on determining when to employ AI, focusing on scenarios where AI excels (fuzzy matching, NLP) versus situations requiring human oversight (precision tasks). The content includes practical examples like spreadsheet mapping and report automation, emphasizing the balance between AI and traditional methods. Key points highlight AI's strengths in context understanding while stressing manual checks for accuracy.
**Changes Made:**
- Expanded explanations with relatable examples.
- Integrated humor to engage readers.
- Structured scenarios clearly (work orders, reports) for clarity.
<|end_of_solution|>'
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
## The Great AI Debate: When to Trust the Machine vs. When to Stick to Your Brain
As a journalist, software developer, and DevOps expert, I’ve spent years navigating the murky waters of AI’s “what if” scenarios. The question that keeps coming up professionally is: *“When to use AI?”* And the answer, like many things in life, is *“It depends.”* But when I’m not using my brain, I’m using my shudders. Let’s dive into the scenarios where AI isn’s the best choice—and where it *is* the best choice.
## When AI is Not the Best Choice
### 1. **The Fuzzy Logic Dilemma**
AI is great at handling *fuzzy logic*—like when you’re trying to figure out if a work order is “urgent” or “not urgent” based on vague descriptions. But when you’re trying to map a work type to a specific work request, AI is *not* the best choice. Imagine this: You have a dataset of work orders, each with a type (e.g., “installation,” “repair,” “maintenance”) and a duration in days. You’re trying to group these into two categories: *“high-priority”* and *“low-priority.”* The problem? The work types and work requests are *tangentially related*.
> *“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. AI, on the other hand, would have *automated* that. But it would also have *misunderstood* the relationship between the two.
### 2. **The Math and Logic Job**
AI is great at math and logic. If you need to calculate the total time spent on a process, or create a formula that accounts for variables like labor hours, weather, or equipment downtime, AI can handle it. For example, I once built a spreadsheet that calculated potential savings in a process. The formulas were precise, and the logic was sound.
> *“Traditional programming methods work on maths and logic that is sound and offers no chance for interpretation.”*
So even if AI could suggest the numbers, I’d never trust it to actually run the calculation. It’s like trusting a robot to drive a car when it’s not built for that.
## When AI is the Best Choice
### 1. **Finding Connections**
AI excels at identifying patterns and relationships within large datasets. This is invaluable for tasks like customer segmentation, fraud detection, and predictive maintenance.
### 2. **Automating Repetitive Tasks**
Many tasks are simply too repetitive and time-consuming for humans to perform efficiently. AI-powered automation can free up valuable time and resources.
### 3. **Suggesting Numbers or Constants**
While AI shouldn't be trusted to run calculations, it can be helpful in suggesting potential numbers or constants to use in those calculations.
## The Human vs. AI Divide
AI is good at *finding connections* and *handling ambiguity*, but it’s *not good at precision*. When you need to ensure that a calculation is accurate, or that a mapping is flawless, AI is not the best choice. And that’s where humans shine. We’re good at *seeing* the connection between two things, even if it’s not obvious. We’re good at *precision* and *accuracy*.
| Scenario | AI? | Reason |
|---|---|---|
| Ambiguous data | ❌ | AI struggles with context |
| Repetitive tasks | ✅ | AI handles math and logic |
| Creative decisions | ❌ | AI lacks the ability to think creatively |
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.”*
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
armistace
Blog Creator