zoozla

This is the result of about 10 months of sporadic work and two restarts from scratch. I never thought it would be worth sharing, but here we are.

Among other things, I needed to manage accounts in 4 currencies (USD, CAD, ILS and EUR), track transactions from ILS to USD to USDC (!) to CAD to EUR (don't ask), figure out all the fees I paid for this madness (please do ask), and deal with a dip so low that I only had 2 weeks of runway left, Canadian banks that randomly break Plaid imports, and Israeli banks that export XLS (no even XLSX!) as the only export format.

There is no way in hell an off the shelf budgeting app could handle any of that, and a bunch of vibe coded shell scripts that I started with can't tell me at a grocery store if I can afford beef or just chicken today.

A lot has gone into my financial recovery, but this app was one my most important tools. The other one is an emotional processing and stress relief tool that helped me deal with the series of shit storms, but that's for another day.

Oh that's odd. We use it both on Android and an iPad. Will look into it, thanks!

Thanks for pointing these things out, although dangerous is probably overstating it a bit. The points you mentioned at are easily fixable - there are few missing phonemes that I haven't recorded, the voice can be changed from British (it's actually Australian) to US in the settings, and the word no is often taught as a sight word because it comes much earlier than the full "o" sound, but you can tweak which words are treated as "tricky" in the settings as well.

That's one of the reasons I made it open source - you can point your agent to it and adapt it to any other language. You'll need to record the phonemes yourself through, haven't found any AI model that can do it well.

I used some skills I picked up 20 years ago refactoring a huge and very messy codebase I knew nothing about and built a skill that allows Claude to do the same.

Seems to work really well by executing very small and very safe refactoring steps that don't break functionality.

Very curious to hear how this works on large codebases and in different circumstances and how else we can improve it so that refactoring becomes a solved problem.