Technical Blog

My current approach is over-engineered for the models I'm using today. I went from around 1,500 words to 150 words—quite a difference.

This approach integrates Claude's chat interface with macOS's automation capabilities, opening up entirely new workflows.

These tools are not the product. They are not universally transformative. They are amazing and though much of the hype surrounding them is arguably unjustified or just plain wrong, I don't believe the excitement is. But this is not the product.

Exploring how context management through reusable prompts, project knowledge bases, and MCP integration creates more effective workflows with language models

In my previous posts I discussed my approach to AI adoption. Now I want to go into more detail on my workflows and show specific examples of how assistants integrate into them.

Over the course of about two months, I had been incorporating assistants more into my workflow—job applications, note-taking systems, a host of templates for common workflows (18+ currently). But I was ready to do more.

What I've found is that you have to find use cases that make sense, at least one to start with, and learn how to interact with AI effectively. Then it becomes easier to see how you can expand into more use cases and integrate it into your workflow.

Building an inventory app to solve a workplace problem showed the value of software that solves practical challenges.