Hello fellow AI enthusiasts! This week I want to start to wind down my AI Newsletter automation/creation story. Up to this point, I walked you through my journey from absolute novice, starting with utilizing Google Gemini on the
gemini.google.com site (I'll call this the retail side), to a more seasoned AI deployment scenario on the development side,
aistudio.google.com. Often times, I would find myself "developing" on the
aistudio.google.com site while interacting with Gemini on the retail side in order to be "coached" along the way, due to a lack of my development skills. Gemini, on the retail side, helped me with prompting, system instructions, and questions on the
aistudio.google.com site itself.
I have to say that AI Studio is certainly an impressive program. However, as my "development" process became more entailed and complex, I found that response times were slower, context memory got used up much quicker, Gemini would implement a function with some code, however the introduction of the new code by Gemini would inevitably interfere with the previous existing codebase, therefore rendering a bug with a previous working function. I found that the collaboration with Gemini, in AI Studio, started becoming tedious and frustrating. I couldn't imagine a more complex development process being too pleasant.
I want to sum up my journey thus far because there are some important distinctions here. It's important to note that my AI Newsletter still required that I create it. This required more coding and development skills than anything. AI helped me tremendously in writing that code. The skills I learned in that part of the journey were prompting, specific instructing, and how to ask the right questions. I told an AI Agent, in this case Gemini, what I wanted to create and Gemini walked me through the whole process, cutting and pasting code within VS Code. This is that Vibe Coding process. Okay for a newsletter creation, but probably not technically sound for a complex program. Once I had the document coded in a way that was formatted how I wanted it to look, I was still responsible for manually inputting the content. For this, I had to spend time going to various websites to get the content I wanted and manually insert the material into previously coded files. This process could be supplemented with an AI Agent, in this case Gemini, by employing an API Key. Now the AI Agent could follow my coded instructions to go get the content that I would normally have to get myself. So, I've used AI in a couple of different ways. One, for overall education and assistance in how to implement my AI Newsletter. Then, I implemented an AI Agent through an API Key, to automate the process. I still had not trained an AI Agent or fine-tuned an AI Agent. While the automation is nice, even the premier LLMs, like Gemini, still make mistakes, hallucinate, create issues that essentially negate the time saved simply doing the task myself.
Let's break down what was accomplished in this couple of month process. The coding and automation all can be done without AI. In fact, it's Microsoft's Task Scheduler that "wakes up the program", not AI. Once the program "wakes up" and calls the AI Agent, with the API Key, the AI Agent begins to perform the tasks. The letter is created for distribution, automatically. However, I would then have to review the letter to make sure it was good to go out. 100% of the time, it was not ready to just go out. It would grab content from the websites that I instructed it to, via web scraping not APIs (Application Programming Interfaces - a software intermediary that allows two applications to talk to each other). This always resulted in the content not being ideally formatted, or the AI Agent would pull AI events from Virginia, not helpful to a Wisconsin newsletter at all. APIs are more reliable, but this requires better programming skills and/or fees by other websites for their API endpoint. Having to review the content and subsequently fix the errors of the AI Agent, work with any bugs of the program, and still create my own creative content, like this section of the newsletter because an AI Agent certainly can not recount my experiences for me, just hasn't been providing the awesome AI experience I was hoping for. I think that this is what many individuals and companies are struggling with regarding AI deployment.
It's clear to me that plugging in AI involves much more effort. For my Newsletter to truly be 100% automated and free of content creation bugs, there would have to be some better coding and prompting. Even then, it would not be prudent for me to just simply allow it to be distributed without review. I wonder if I could ever get it to pass a review 100% of the time with no revisions required at all. Stay tuned for more conversation about AI development. I will continue to play with my Newsletter experiment and will provide any updates that may improve the process. However, future articles will shift a focus to more than just this newsletter creation. Hopefully, we can uncover some better use cases for AI deployment. Have a great rest of the week!