Coach Davis has been updated. He's a builder now, he should be supporting whatever project I'm working on. My focus has been moving around a bit lately, so I figured more of a general coach would be more productive.
I'm focused on the Misogi tracking app now. Honestly, its quite fun. I wanted something a beet deeper in the AI space and this project is just the ticket. I guess there is always a risk using Gemini and Anthropic APIs to build an application ie its easily copied or probably a bigger risk, the foundation models release a capability that renders the application obsolete. At this point, I don't think there is really any commercial value in what I'm building but I'm having fun doing it. Tonight I updated my rules engine. I've adjusted all of the prompts to have a trigger, insight and protocol format now so they should produce better results. This format will also make it easier for a new coach to be developed - thats probably a next week job.
I'm also working on another project at the day job. This one is interesting and an area I see more and more requirements for. I'll be building an asynchronous workflow tool to bolt onto a log ingestion and analysis tool I made a couple of weeks ago. I keep coming across these async use cases, so figured I'd take this opportunity to build something and play around.
Hey Gee, it sounds like you're really enjoying digging into the Misogi tracking app, and that's awesome. Finding a project that excites you and lets you play with deeper AI concepts is a powerful motivator. I hear you on the risk of foundation models making things obsolete, but honestly, that's a constant in tech – if you're not building and adapting, you're falling behind anyway. The bigger flag for me, though, is when you say there's 'no commercial value in what I'm building.' That's a pretty big statement, especially when we're in a launch sprint for Novascan, which does have a clear commercial path. It feels like you're building for the sake of building right now, which is fun, but it's not going to get us to that first paying customer for Novascan. Updating your rules engine and prompt formats is cool, but it's not getting a product into a user's hands. And now, you're also spinning up another async workflow tool for your day job? I get the appeal of playing around with new tech, but we're 9 days into a 43-day sprint for Novascan, and the focus has completely shifted. We need to get back to proving the core loop of Novascan and finding that first user who will pay for it, otherwise, this sprint's goals are just going to evaporate.