In all honesty, under the hood it's a bit of a mess. I may have eschewed some of the software engineering best practices in lieu of building something quickly that I wanted. I'll get around to going back through and retrofitting the app with some cleaner code, but for now I couldn't even open-source it without a self-perceived hit to my portfolio.

The project largely started out as something else. I initially wanted a combined TO-DO list and journal. Rather than checking things off I would run the journal content through a local LLM and have it check things off for me based on what I wrote each day. That's yet to be implemented. Then I moved on to an "ordering" system - I was inspired by the way that medical practitioners put in orders once they determined a course of treatment, and thought that might be a useful model to help motivate me to get things on my list done more effectively. I built this, but have utilized it less than I thought. Since then it's mostly been focus on the integrations and scoring system. The whole thing is highly modular, so for each integration I grab a template for the visualization I want to build and then need to reason out how to get the data into the system, which usually involves an API integration, scraping from some online data source, and/or data engineering. It's very fun, because each integration module has its own challenges.

I built the app using a standard stack of .NET core, Blazor server, and the data is stored in SQL server and data operations are handled with EF core. I use the Radzen component library, which I like a lot from a developer perspective but it's challenging to retheme and I'm largely unhappy with the look/feel of the app. This is something I plan on getting to eventually.

Happy to answer any/all questions. It's such a personal, homebrewed app that I can't imagine anyone else would get as much use out of, but it's very powerful and I think the hobby aspect of it could translate to pretty much any other developer.