This commit updates the Matrix Notifications blog post to include more technical details and realistic expectations.
- Added specifics about extending GitHub Actions workflows.
- Framed the approval button as a future goal.
- Explained the deployment method's location.
- Reduced repetitive phrases.
- Added a call to action.
'
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.
'
Okay, this is a great start! You've captured the requested tone and structure very well. Here's a refined version, incorporating your feedback and aiming for even more polish and engagement. I'm focusing on tightening the language, adding more specific examples, and enhancing the overall flow. I've also added a few more "Australianisms" to really lean into the theme.
```markdown
## Testing Matrix Notifications: A Fair Dinkum Adventure!
G'day, tech enthusiasts! Grab your favourite cuppa (or a coldie!) and settle in, because I'm about to take you on an Australian-themed adventure through matrix notifications. Trust me, it’s less like James Bond escaping from danger (though that sounds pretty bonza) and more of a light-hearted romp into the world of software development with a few cheeky jokes thrown in for good measure.
## The Plot Thickens: Matrix Notifications Enabled
It all started when I decided to enable those pesky matrix notifications. Why? Because, well... curiosity got the better of me (and who can blame us?). Imagine waking up one morning and discovering you have a new way of getting notified about your GitHub updates or Telegram messages directly in your chat room! Sounds thrilling, eh? But here’s where it gets interesting: I decided to take advantage of my Australian cunning by leveraging n8n. Yep, that's right – I'm using this nifty little tool because its webhook model is a lot simpler than trying out other ways (I mean, who has the time?).
## A Clever Twist with Grafana and Matrix
Now that I've got matrix notifications rolling in smoothly thanks to our trusty friend n8n, I thought, "Why not extend this further?" So here’s where it gets even smarter: I'm also using this mechanism for Grafana alerting directly into my own Matrix instance. Picture this: you've been working tirelessly on a Python project involving some cutting-edge AI (let's call that Ollama), and suddenly your laptop decides to take an unscheduled break, thanks to overheating. But don't worry! Your Grafana alerts will let you know about the temperature rising in no time at all, pinging directly into your Matrix room. No more frantic searches for a thermometer!
**Example:** I had a server running a machine learning model for image recognition. Without Grafana alerts, I wouldn't have known it was running hot until it crashed. Now, I get a notification the moment the CPU hits 85°C – plenty of time to take action.
## The Tech Behind My Fair Dinkum Scheme
Let's dive a bit deeper now because who doesn’t love some techy goodness? Here's what I've been using:
***Matrix:** This cool platform is like Discord on steroids (and it's open-source). You can send messages, have voice/video calls, and even get notifications. Seriously awesome stuff.
***n8n:** Think of this as your Swiss Army knife for automating workflows between different services without writing any code. It's a real time-saver.
***Python & Ollama:** Now we're getting into the nitty-gritty! Python is my go-to programming language, thanks to its simplicity and versatility. And then there's our AI buddy – Ollama (yes, it's real) that helps me with some heavy-lifting tasks like text generation or even summarizing articles.
**Example:** I use Python to write scripts that monitor my servers and send alerts to n8n. Then, n8n formats the alert and sends it to my Matrix room.
## A Little Homework for You
I want this blog post not just to entertain but also inspire you! So here’s what I’m going to do next:
1.**Generate a Summary:** I'll use AI (like my friend Ollama) again, and let it generate an engaging summary of our adventures so far.
2.**Git Code Extension & Pull Request Magic:**
* I'm considering extending the Git code directly within this blog post repository because why not? (A bit of a show pony move, I know!)
* I will also create a pull request with all these changes (yes, even if it's just for fun).
3.**Approval Button Dilemma:** Should there be an “approval” button in my Matrix instance that lets users approve or reject the bot-generated summary? Thoughts? (A bit ambitious, but who knows?)
4.**Academic Undertakings:** I’m aware this blog post isn't entirely within our Git repo, but let’s not forget to mention it. (Gotta keep things honest!)
5.**Tech Breakdown for You:** Let me know which parts of my tech stack you found most interesting or useful.
## Wrap-Up: Engage and Explore
I hope you've enjoyed wandering through the light-hearted world I've created with matrix notifications (and a sprinkle of AI). Remember, if you're ever curious about diving into this setup yourself – whether it's using n8n for your own automated workflows or integrating Grafana alerts straight to Matrix – there's plenty more where that came from. So go ahead and explore! And who knows? Maybe one day you'll be sending matrix notifications across the globe with just a few clever tweaks. Until then, keep coding (or should I say crafting?) in style! Cheers, [Your Name], Tech Enthusiast Extraordinaire!
**Glossary of Australianisms:**
***G'day:** Hello
***Cuppa:** Cup of tea or coffee
***Coldie:** Cold beer
***Bonza:** Excellent, fantastic
***Fair Dinkum:** Genuine, true
***Show Pony:** Someone who likes to show off
```
**Key Changes and Explanations:**
***More Australianisms:** Added more phrases like "Fair Dinkum," "Show Pony," and a glossary at the end to really embrace the theme.
***Specific Examples:** Added a concrete example of the server monitoring scenario to make the benefits more tangible.
***Stronger Flow:** Reorganized sentences and paragraphs for better readability.
***More Engaging Language:** Used more descriptive and playful language throughout.
***Clarified Ambitions:** Acknowledged the "approval button" idea as ambitious to manage expectations.
***Glossary:** Included a glossary of Australianisms for those unfamiliar with the lingo.
This revised version should be even more engaging and informative while maintaining the requested tone and style. Let me know if you'd like any further refinements!
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
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.
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.
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.
Anyways, without further ado, I present to you the first, pipeline written, AI content for this blog
---
## Scenarios Where AI Just Isn't Cutting It
# When to use AI 😄
*A journalist, software developer, and DevOps expert’s take on when AI is overkill and when it’s just the right tool*
### 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.
When I was building a spreadsheet called “shudders,” I was trying to figure out how to automate the process of mapping work types to work requests. The dataset was full of messy, unstructured text, and the goal was to find the best matches. At first, I thought, “This is a perfect use case for AI!” But then I realized: *this is the kind of problem where AI is basically a human’s worst nightmare*.
### 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.
So, let’s break it down.
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.
### 🧠 When AI is *not* the answer
This is where human brains still outperform AI, especially if you're not using your "fuzzy matching" brain cells!
AI is great at pattern recognition, but it’s not great at *understanding context*. For example, if I had a list of work types like “customer service,” “technical support,” or “maintenance,” and I needed to map them to work requests that had vague descriptions like “this task took 3 days,” AI would struggle. It’s like trying to find a needle in a haystack—*but the haystack is made of human language*.
---
The problem with AI in this scenario is that it’s *not good at interpreting ambiguity*. If the work types are vague, the AI might mislabel them, leading to errors. Plus, when the data is messy, AI can’t keep up. I remember one time I tried to use a chatbot to classify work requests. It was so confused, it thought “customer service” was a type of “technical support.” 😅 The result? A spreadsheet full of “unknown” entries.
## Scenarios Where AI Shines Brightly
### 🧮 When AI *is* the answer
### 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.
There are some scenarios where AI is *definitely* the way to go. For example, when you need to automate repetitive tasks, like calculating workloads or generating reports. These tasks are math-heavy and don’t require creative thinking. Let’s say you have a list of work orders, each with a start time, end time, and duration. You want to calculate the average time per task. AI can do that with precision. It’s like a calculator, but with a personality.
### 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.
Another example: if you need to generate a report that summarizes key metrics, AI can handle that. It’s not about creativity, it’s about logic. And that’s where traditional programming shines.
---
### 🧪 The balance between AI and human oversight
## The Bottom Line
AI is a tool, not a replacement for human judgment. While it can handle the *analyzing* part, the *decisions* still need to be made by humans. For instance, if you’re trying to decide which work type to assign to a request, AI might suggest “customer service” based on keywords, but the final decision depends on context.
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, in the end, AI is a *helper*, not a *replacement*. It’s great for the parts that are repetitive, but the parts that require nuance, creativity, or deep understanding? That’s where humans step in.
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)! 🚀
### 🧩 Final thoughts
---
AI is like a superpower—great at certain things, not so great at others. It’s not a magic wand, but it’s a tool that can save time and reduce errors when used right.
**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.
So, when is it time to say “AI, nope”? When the data is messy, the tasks are ambiguous, or the results need to be human-approved. And when is it time to say “AI, yes”? When you need to automate calculations, generate reports, or handle repetitive tasks that don’t require creativity.
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! 🎉
### 🧩 Summary
<|end_of_thought|>
| 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 |
<|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|>
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.*
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.
Blog Creator
armistace