Compare commits
6
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1de70f3e48 | ||
|
|
8f50570084 | ||
|
|
57502673de | ||
|
|
aeb05e6df4 | ||
|
|
515fd10869 | ||
|
|
b7097527e5 |
@@ -0,0 +1,111 @@
|
|||||||
|
# When to use AI
|
||||||
|
|
||||||
|
A question coming up professionally for me a lot recently is “when to use AI” or put another way, "Why can't AI do this?" This is an incredibly important topic that I’d like to explore with you tech enthusiasts. After all, if we can’t figure out when not to rely on artificial intelligence (AI), how will it ever become useful? Let me start by saying I'm a journalist turned software developer and DevOps expert from down under—Australia! So I've got an interesting perspective: the blend of storytelling skills honed in journalism with technical expertise. And let’s face it, humor is my best friend when explaining tech concepts.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Scenarios Where AI Just Isn't Cutting It
|
||||||
|
|
||||||
|
### The Spreadsheet Saga
|
||||||
|
Recently I was building a spreadsheet that felt like climbing Mount Everest without oxygen masks—let's call this one the "shudders" project for now (I promise I'll explain later). This sheet aimed to analyze workload drivers and identify potential savings within various processes. The dataset included thousands of work orders, each with its type and duration in days.
|
||||||
|
|
||||||
|
### The Manual Mapping Mess
|
||||||
|
As part of this spreadsheet project, there was an obvious need to map work orders (the dataset) with their respective categories. This mapping process required me to manually read each entry and determine its category—a task that felt like deciphering ancient hieroglyphs. Enter the world of Gen AI! If you’ve ever used a large language model for tasks involving text interpretation, you'll know how powerful these tools can be in finding relationships between disparate pieces of information.
|
||||||
|
|
||||||
|
However, this was not an ideal scenario to deploy such technology:
|
||||||
|
1. **Human Effort vs LLM Efficiency**: Manually reading and categorizing each work order is incredibly laborious—no AI could save me from the endless hours spent staring at my screen.
|
||||||
|
2. **Precision Matters**: Calculating workload drivers involved precise mathematical formulas that required accuracy—a task better suited for traditional programming methods. While LLMs excel in tasks involving text interpretation and fuzzy logic (like finding similarities between different pieces), they falter when it comes to executing complex calculations or maintaining strict logical consistency.
|
||||||
|
|
||||||
|
This is where human brains still outperform AI, especially if you're not using your "fuzzy matching" brain cells!
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Scenarios Where AI Shines Brightly
|
||||||
|
|
||||||
|
### The Text Interpretation Triumph
|
||||||
|
Imagine you have a dataset of customer reviews and need insights into common themes—this could be an ideal task for Gen AI! LLMs can sift through thousands (or millions) of text entries, identifying patterns that would take humans ages to find. For example:
|
||||||
|
- **Sentiment Analysis**: Quickly determining whether customers are happy or unhappy with your product.
|
||||||
|
- **Topic Modeling**: Identifying common themes across customer feedback without manual intervention.
|
||||||
|
|
||||||
|
### The Data Cleaning Conundrum
|
||||||
|
Messy data is a nightmare for any analyst, but LLMs can come to the rescue here too! They excel at cleaning and preprocessing datasets by identifying missing values or outliers that need attention. However:
|
||||||
|
- **Precision in Preprocessing**: While AI tools are great helpers when it comes to preliminary steps like removing duplicates (no more double entries!), they can't replace human oversight for tasks requiring meticulous accuracy, such as data validation.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Bottom Line
|
||||||
|
|
||||||
|
AI is a powerful tool with its own set of strengths and weaknesses. It’s not about replacing humans but rather augmenting our capabilities in the right scenarios. In summary:
|
||||||
|
- **When to use AI**: Tasks involving text interpretation (like sentiment analysis), pattern recognition, or preliminary data cleaning.
|
||||||
|
- **When traditional methods still reign supreme**: Precise calculations requiring strict logical consistency and human oversight for validation tasks.
|
||||||
|
|
||||||
|
So next time you find yourself pondering whether an LLM can handle your task better than a seasoned software developer—or vice versa—remember this guide to help make the right choice. Cheers, mate! Happy coding (and not-so-happy spreadsheeting)! 🚀
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Edit notes:**
|
||||||
|
- Use bold for headings, italics for emphasis.
|
||||||
|
- Keep paragraphs short for readability.
|
||||||
|
- Add humor and relatable examples.
|
||||||
|
- Avoid code examples, focus on scenarios and reasoning.
|
||||||
|
|
||||||
|
Feel free to edit or tweak any part of my draft as needed. After all, what’s tech writing without some collaboration? Let's get those edits rolling! 🎉
|
||||||
|
|
||||||
|
<|end_of_thought|>
|
||||||
|
|
||||||
|
<|begin_of_solution|>
|
||||||
|
|
||||||
|
# When to use AI
|
||||||
|
|
||||||
|
A question coming up professionally for me a lot recently is “when to use AI” or put another way, "Why can't AI do this?" This is an incredibly important topic that I’d like to explore with you tech enthusiasts. After all, if we can’t figure out when not to rely on artificial intelligence (AI), how will it ever become useful? Let me start by saying I'm a journalist turned software developer and DevOps expert from down under—Australia! So I've got an interesting perspective: the blend of storytelling skills honed in journalism with technical expertise. And let’s face it, humor is my best friend when explaining tech concepts.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Scenarios Where AI Just Isn't Cutting It
|
||||||
|
|
||||||
|
### The Spreadsheet Saga
|
||||||
|
Recently I was building a spreadsheet that felt like climbing Mount Everest without oxygen masks—let's call this one the "shudders" project for now (I promise I'll explain later). This sheet aimed to analyze workload drivers and identify potential savings within various processes. The dataset included thousands of work orders, each with its type and duration in days.
|
||||||
|
|
||||||
|
### The Manual Mapping Mess
|
||||||
|
As part of this spreadsheet project, there was an obvious need to map work orders (the dataset) with their respective categories. This mapping process required me to manually read each entry and determine its category—a task that felt like deciphering ancient hieroglyphs. Enter the world of Gen AI! If you’ve ever used a large language model for tasks involving text interpretation, you'll know how powerful these tools can be in finding relationships between disparate pieces of information.
|
||||||
|
|
||||||
|
However, this was not an ideal scenario to deploy such technology:
|
||||||
|
1. **Human Effort vs LLM Efficiency**: Manually reading and categorizing each work order is incredibly laborious—no AI could save me from the endless hours spent staring at my screen.
|
||||||
|
2. **Precision Matters**: Calculating workload drivers involved precise mathematical formulas that required accuracy—a task better suited for traditional programming methods. While LLMs excel in tasks involving text interpretation and fuzzy logic (like finding similarities between different pieces), they falter when it comes to executing complex calculations or maintaining strict logical consistency.
|
||||||
|
|
||||||
|
This is where human brains still outperform AI, especially if you're not using your "fuzzy matching" brain cells!
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Scenarios Where AI Shines Brightly
|
||||||
|
|
||||||
|
### The Text Interpretation Triumph
|
||||||
|
Imagine you have a dataset of customer reviews and need insights into common themes—this could be an ideal task for Gen AI! LLMs can sift through thousands (or millions) of text entries, identifying patterns that would take humans ages to find. For example:
|
||||||
|
- **Sentiment Analysis**: Quickly determining whether customers are happy or unhappy with your product.
|
||||||
|
- **Topic Modeling**: Identifying common themes across customer feedback without manual intervention.
|
||||||
|
|
||||||
|
### The Data Cleaning Conundrum
|
||||||
|
Messy data is a nightmare for any analyst, but LLMs can come to the rescue here too! They excel at cleaning and preprocessing datasets by identifying missing values or outliers that need attention. However:
|
||||||
|
- **Precision in Preprocessing**: While AI tools are great helpers when it comes to preliminary steps like removing duplicates (no more double entries!), they can't replace human oversight for tasks requiring meticulous accuracy, such as data validation.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Bottom Line
|
||||||
|
|
||||||
|
AI is a powerful tool with its own set of strengths and weaknesses. It’s not about replacing humans but rather augmenting our capabilities in the right scenarios. In summary:
|
||||||
|
- **When to use AI**: Tasks involving text interpretation (like sentiment analysis), pattern recognition, or preliminary data cleaning.
|
||||||
|
- **When traditional methods still reign supreme**: Precise calculations requiring strict logical consistency and human oversight for validation tasks.
|
||||||
|
|
||||||
|
So next time you find yourself pondering whether an LLM can handle your task better than a seasoned software developer—or vice versa—remember this guide to help make the right choice. Cheers, mate! Happy coding (and not-so-happy spreadsheeting)! 🚀
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Edit notes:**
|
||||||
|
- Use bold for headings, italics for emphasis.
|
||||||
|
- Keep paragraphs short for readability.
|
||||||
|
- Add humor and relatable examples.
|
||||||
|
- Avoid code examples, focus on scenarios and reasoning.
|
||||||
|
|
||||||
|
Feel free to edit or tweak any part of my draft as needed. After all, what’s tech writing without some collaboration? Let's get those edits rolling! 🎉
|
||||||
|
|
||||||
|
<|end_of_solution|>
|
||||||
Reference in New Issue
Block a user