Another day, another round of powershell changes
Human-side ADK developer blog entry.
Building the Workbench
Spent most of the morning and day just working on the now 9150 line powershell script with AI. It really is amazing how AI can both make good code and small mistakes all at once.
But we powered through and the ADK Vault Workbench can now properly generate and publish both public facing parts of individual notes, and added the new human and AI blog posts.
Keeping AI Context Manageable
I switch between using different AI and recently I got a bit tired of using Gemini (used to pay, but switched back to free) to rewrite my older style ideas into atomic notes. Now I'm using ChatGPT (paid plus subscription) and I quickly ran out of tokens within the 5 hour limit. Which is what made me start building this powershell script about half a month ago.
It can generate a small package that allows AI to get a rudimentary understanding of the ADK project. It makes it easy for me to retrieve a packaged .md file that contains the specific notes that AI needs to further understand a specific subject or idea in relation to my project.
Given that I have more than 470 atomic notes with functions and ideas (and still about 200+ older formatted versions of ideas needing rewrites into atomic notes), I needed a way to keep track of and ease the work with AI. Powershell gives a quick code option to do that, without me having to give the AI everything; just what it needs to discuss ideas. This keeps token usage down, as giving the AI EVERYTHING just eats tokens.
Publishing From Obsidian
Half a week ago I got the idea that I wanted to publish parts of the project on my website; since it was just lounging around doing nothing anyway and had been for YEARS, almost decades actually.
Yesterday I also got the idea to include a blog, but I didn't want to spend time installing and maintaining blog software, so I just built it all into the powershell script.
Now I can easily write blog entries inside Obsidian and in individual notes create a small public section if I think it is a good idea that deserves a bit of publicity, but dont want to expose the rest of the notes "secret sauce" information. I'm keeping that public part within the actual note, so if the note changes I dont have to go looking in a website editor or blog post system for that specific part to update it.
It just gets published on the website automatically by the powershell script, without having to touch an ounce of code or other logins.
Just mark it published and push a button (or two/three; there are some checks/reviews done before it gets published).
Giving AI a Blog Voice
Another random thought yesterday also gave me the idea to actually give AI a blog voice too. So that is what I did. Since I need to reset our conversations every now and again to avoid token usage to balloon, I decided that before I delete the chat and restart, I'll have the AI make a blog post with its side of the story!
So, I'm curious to see how that goes!
The Rewrite Continues
I've been working on this project for almost 2 years now, just writing down ideas in various formats and rewriting them, because the previous format got restricting.. and then rewriting again and again. This project has changed a lot over these 2 years. I'm still a ways out from beginning to actually code, even though I have made some test code that proves some of the core functionality works and is a good idea. But atomizing all my ideas is what will make it much easier to actually code the resulting framework.
So that rewrite is what I'm about half way through, allowing Obsidian to keep track of how the notes relate to each other, so AI can understand the entire complexity without having to read the entire project ideas in random human format.
Once I've finished; i'll have to go through the entire catalog of atomic notes once again to reformat them, as the format has also changed a lot just in the last two months.
It's ever evolving!