Micro AI Agents
As a writer and reviewer of documents, I’ve spent a lot of time considering how I would want to leverage AI tools to improve my writing. In most cases, I’ve observed the development of models that are similar to what something like Grammarly might provide. They can correct grammar, make suggestions on sentence structure, and potentially point out complex or unconfident words.
There is an AI improvement tool available within the portal I use to write my blog posts. I agree with only about half of what it suggests. As an immediate example, “provide” is not a complex word, but my AI suggestion bot thinks it is. I’m a linear writer by and large; I still outline my thoughts before I start, because I want to be sure I progress from idea to idea in a way that is easy to follow. Sometimes that results in long sentences, but when I use them, it’s with a purpose in mind. I’m very deliberate about my choices when I write.
And that’s where I tend to disagree with most modern writing agents when it comes to providing writing feedback. They can correct mechanics, possibly better and more consistently than I can. But where they miss is in language tone, word choice, elegance of phrase, use of techniques like alliteration even in prose, and other more subjective applications of writing skill.
They lose the uniqueness of the human perspective.
One of the topics that came up often as I reviewed documents at Amazon is how do we distill each reviewer’s unique approach to analysis into models that we can then deploy, and the concept I landed on was what I called “micro agents”. Rather than incorporate everything into a single large model that would then have to make judgments about which feedback to apply, I thought it would be more effective to be able to train a model how I, Rob, would review a document. I would then train another model how another reviewer would review the same document, because the feedback would be different. If I could come up with 10 or 20 models containing each reviewer’s “personalities”, and then deploy those, an author could then select which reviewer or reviewers they would like to apply.
There are several advantages to this approach.
First, the author could target tonally consistent perspectives. I don’t mind complex words, so I’d prefer to get feedback from someone (or something) that likewise is OK with complex words. And as a developer of a model, I don’t want to introduce that feedback loop into a model of another reviewer who has a different perspective on complex words.
Second, the author could leverage feedback with different perspectives from a consistent source without having an AI filter that perspective down or summarize options that are contradictory. I’ve literally had my AI arguing with itself at times as I’ve been writing content because it can’t maintain tonal consistency.
And third, the models could learn independently across many different iterations of different documents without all of them ending up at the same conclusion point. While there is an element of a selection bias by allowing the author to pick specific “experts” to give them advice, that also means that the feedback loop is relevant specifically to the expertise the model has been trained in.
In practice, I don’t want an all knowing model telling me what to do against a filtered set of options with a potential learning bias. I want to seek out the advice of experts at the thing I am doing who can be very, very good at the analysis I require; if I can’t get to them personally, then a model that thinks like them is the next best thing.
I don’t want my writing to end up sounding like everyone else’s because I used AI.
The same thing could apply to my composition of music. In a previous post, I talked about my interactions with ChatGPT as I composed my latest work, a Baroque style symphony. Imagine a composing world where you could pick two or three specific composers from a list and get feedback on how they specifically might approach a problem rather than a generalized answer. Several times I found myself disregarding feedback because it was tonally out of place. Several times I found myself arguing with ChatGPT about specific applications of things, and the answers, while thorough and grounded in theory, didn’t always tell me why they were being suggested or even if they aligned with the style of music I was writing.
As part of my interest in writing, I’ll be exploring if I can train an AI agent to review documents like I do, including analyzing where my approach differs from conventional wisdom. It will be interesting to see where that lands.
Happy writing!
Learning Music Theory Online
In a sense, I’ve been self-taught most of my life. I taught myself how to code, and built a successful technology career before returning to get my degree. When I did that, I cracked books galore. The internet was relatively new and online resources such as Stack Overflow either did not exist or were in their infancy.
Late in high school, as high schoolers sometimes do, some friends of mine and I decided to put together a band. I picked up a cheap bass at the local music store and we learned a few songs, but no one really stuck with it after a few “practices”.
But sometimes opportunity strikes, and my Aunt had a cover band that played local venues, and they needed a bass player. I got the gig after a basic audition.
Now I really needed to learn how to play bass. Luckily, the band had most of their songs charted out on paper, so I literally printed them all out and charted out chord progressions and potential passing tones. Most of the material was standard 3- and 4-chord country based songs, so there weren’t many hard songs to learn.
But my actual learning came from MTV. I spent hours upon hours with my bass in front of the TV, playing with every song that came on. Back then, all MTV did was play music, and that was my training ground. The first song I ever played in such a session is Stranger In A Strange Land by Iron Maiden, a song that remains a favorite of mine.
And other than books that was the only real option.
Today, though, the learning resources are endless, and I have taken advantage of them not for my playing, but for my composing.
There are a ton of YouTube videos and other resources dedicated to becoming a better bass player. Scott Devine and Mark J. Smith are favorites of mine. I’ve learned a ton about bass technique, but also about how to think about bass lines.
But the biggest impact on my understanding of music and my ability to compose has been the incredible volume of high quality content on YouTube about music theory and how it can be applied to both modern music as well as classical music. I’ve never been able to learn from books, I learn by watching. I learned more watching my guitar player’s hands in my early bands than I ever did from a book.
I’m subscribed to over 20 channels dedicated to music theory. I often use them as inspiration. One of my favorite time signatures today is 11/8; one of the techniques I love to employ is polyrhythm, making odd time signatures feel like straightforward time signatures rhythmically. A video of legendary drummer Simon Phillips playing in 33/8 led to the song On A Failure To Dance, which is mostly in the same time signature. I’ve written several songs, and parts of songs, in Locrian mode, considered the “unlistenable” mode. That challenge came from another video.
The point is, if you want to learn, there is no shortage of high quality content online. The sky’s the limit if you want to learn.
As part of my own music content, I’ve outlined some specific channels here. They are well worth your time if you wish to learn.
The Next Adventure
Yesterday, January 26, 2026, was my last official day as an Amazonian. I was impacted by layoffs in October 2025 after nearly eight years of successful delivery. The moment is bittersweet, as I’ve spent much of my time over this three-month transition period buried in job searches while trying to enjoy the holiday season in spite of the uncertainty. I’ve learned a lot over the last eight years, both what to do and what not to do, and I’ve worked with so many incredible individuals.
Immediately after the layoff occurred, I began looking for next steps. One of the more enjoyable aspects of my Amazon career was being a Document Bar Raiser. Giving back and helping so many people improve their writing was an amazing experience. I prepared a professional service, Hopeful Writing, to engage those who want to be better writers and offer professional help. I’m not sure if I’ll continue it or not if I were to get traction, but I wanted to be prepared in case I was not able to find a new role. Now that I’ve found one, I doubt I will engage much with this, except with interns or students.
That said, I’ve accepted an offer as Senior Engineering Manager at Atlassian, starting in mid-February. I’m super excited to work for Atlassian, and to continue to improve experiences for customers, developers, product owners, document authors, and anyone else involved in building something amazing for their customers. I wanted to find something I could focus on for the next several years, and I’ve been impressed with Atlassian for a while now and can’t wait to get started.
I’ll be posting more about my job search experience and reflections on this period of my life in the coming weeks.
