zlacker

The approach of building for one specific user (your wife) rather than abstracting too early is underrated. You end up with something that actually fits the workflows instead of a generic tool that needs heavy configuration.

Elixir + Ash is an interesting choice for this domain. LiveView particularly shines for internal tools like this where you want the interactivity without managing a separate frontend build. Curious how the AI code generation worked with Ash specifically - the declarative nature seems like it could either help a lot (clear patterns) or confuse models that expect more explicit code.

The BOM with cost rollups is the feature that would have saved me hours in a previous project. Most small batch producers I know either overprice everything out of caution or underestimate costs because tracking ingredient pricing through recipes is tedious in spreadsheets.

>>Soeren+(OP)
Elixir + Ash is so good, and AI works very well with it because it can understand the domain you are working in. LiveView is amazing, not just for internal tools. I would even say that in most cases it will outperform flashy UIs, because it focuses on actual users who work with the app every day, not people who just want to be impressed for a minute

>>Soeren+(OP)
I love this so much. I do worry about the hidden cost of maintaining these software stacks that have a userbase of one. Things like hidden vulnerabilities, bugs, and edge cases that could bring a business down for days.

But I do think the days of just having to learn, tolerate, and accept any commercial software stack for your business because it's too complex to build yourself are over. What vendors remain will have to absolutely meet users with their unique requirements and budget.