Compare commits

...
Author SHA1 Message Date
armistace e7f996306f Human edit and update 2025-06-06 12:30:42 +10:00
Blog Creator 22c521293f 'Clarify AI usage scenarios effectively.' 2025-06-06 02:28:07 +00:00
Blog Creator 74f8c8607b 'Add clarity on AI limitations.' 2025-06-06 01:57:04 +00:00
+41 -42
View File
@@ -1,10 +1,10 @@
Title: When to use AI Title: When to use AI
Date: 2025-06-05 20:00 Date: 2025-06-05 20:00
Modified: 2025-06-06 08:00 Modified: 2025-06-06 08:00
Category: AI, Data Category: AI, Data
Tags: ai, python Tags: ai, python
Slug: when-to-use-ai Slug: when-to-use-ai
Authors: Andrew Ridgway Authors: Andrew Ridgway
Summary: Should we be using AI for ALL THE THINGS!? Summary: Should we be using AI for ALL THE THINGS!?
@@ -15,62 +15,61 @@ Well.. today is the first day that the automated pipeline has generated content
2. Notification to Matrix that something has happened 2. Notification to Matrix that something has happened
3. Updating Trilium so that the note is marked as blog_written=true 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 BUT it can take a note from trilium, generate drafts with mulitple agents, and then use RAG to have an editor go over those drafts.
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. I'm particularly proud of the randomness I've applied to temperature, top_p and top_k for the different draft agents. This means that each pass is giving me quite different "creativity" (as much as that can be applied to an algorithm that is essentially munging letters together that have a high probability of being together) It has created some really interesting variation for the editor to work with and getting some really interesting results.
## When AI is Not the Best Choice Anyways, without further ado, I present to you the first, pipeline written, AI content for this blog
### 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*. # When to Use AI: Navigating the Right Scenarios
> *“I was given a list of work types that could be grouped into 1 of 2 categories exclusively.”* Okay, so I've been getting this question a lot lately: "When should we use AI?" or even more frustratingly, "Why can't AI do this?" It's like asking when to use a hammer versus a screwdriver. Sometimes AI is the perfect tool, other times it's better left in the toolbox. Let me break down some scenarios where AI shines and where it might not be the best bet.
> *“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. ## The Spreadsheet Dilemma: Where AI Fails
### 2. **The Math and Logic Job** **Scenario:** Mapping work types to categories in a spreadsheet with thousands of entries, like distinguishing between "Painting," "Repainting," "Deck Painting," or "Stucco Repainting."
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. **Why AI Struggles Here:**
> *“Traditional programming methods work on maths and logic that is sound and offers no chance for interpretation.”* * **Fuzzy Matching & Contextual Understanding:** AI excels at interpreting relationships between words (e.g., recognizing "Deck Painting" as a subset of "Painting"). However, traditional methods with regex or string manipulation fail here because they lack the nuanced judgment needed to handle ambiguity.
* **Precision Over Ambiguity:** Calculations requiring exact values (e.g., average durations) are better handled by deterministic algorithms rather than AI’s probabilistic approach.
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. **Traditional Methods Win Here:**
## When AI is the Best Choice * **Formula-Based Logic:** Building precise formulas for workload analysis relies on clear, unambiguous rules. AI can’t replace the need for human oversight in such cases.
### 1. **Finding Connections** ## When AI Shines: Contextual and Unstructured Tasks
AI excels at identifying patterns and relationships within large datasets. This is invaluable for tasks like customer segmentation, fraud detection, and predictive maintenance. **Scenario:** Automating customer support with chatbots or analyzing social media sentiment.
### 2. **Automating Repetitive Tasks** **Why AI Works Here:**
Many tasks are simply too repetitive and time-consuming for humans to perform efficiently. AI-powered automation can free up valuable time and resources. * **Natural Language Processing (NLP):** AI understands context, tone, and intent in unstructured data, making it ideal for tasks like chatbot responses or content analysis.
* **Pattern Recognition:** AI identifies trends or anomalies in large datasets that humans might miss, such as predictive maintenance in industrial settings.
### 3. **Suggesting Numbers or Constants** ## Hybrid Approaches: The Future of Efficiency
While AI shouldn't be trusted to run calculations, it can be helpful in suggesting potential numbers or constants to use in those calculations. While traditional methods remain superior for precise calculations, AI can assist in setting up initial parameters or generating insights. For example:
## The Human vs. AI Divide * **AI Proposes Formulas:** An LLM suggests a workload calculation formula based on historical data.
* **Human Checks Validity:** A human ensures the formula’s accuracy before deployment.
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*. ## Key Takeaways
| Scenario | AI? | Reason | 1. **Use AI** for tasks involving:
|---|---|---| * Unstructured data (e.g., text, images).
| Ambiguous data | ❌ | AI struggles with context | * Contextual understanding and interpretation.
| Repetitive tasks | ✅ | AI handles math and logic | * Pattern recognition and trend analysis.
| Creative decisions | ❌ | AI lacks the ability to think creatively | 2. **Stick to Traditional Methods** for:
* Precise calculations with deterministic logic.
* Tasks requiring error-free accuracy (e.g., financial modeling).
So I had to manually read each work type and map it to a work request. It was a *shudder-inducing* task. ## Conclusion
## The Final Thought AI is a powerful tool but isn’t a one-size-fits-all solution. Match the right approach to the task at hand—whether it’s interpreting natural language or crunching numbers. The key is knowing when AI complements human expertise rather than replaces it.
So, in summary: **Final Tip:** Always consider the trade-offs between precision and context. For tasks where nuance matters, AI is your ally; for rigid logic, trust traditional methods.
* **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.”*