|
|
|
|
|
by senko
174 days ago
|
|
> a deterministic problem (substring matching transaction descriptions) that could be solved with a 50-line Python script I don't know about your bank transactions, but at least in my case the descriptions are highly irregular and basically need a hardcode for each and every damn pos location across each of the store location across each vendor. I attempted that (with a Python script), gave up, and built myself a receipt tracker (photo + gemini based ocr) instead, which was way easier and is more reliable, even though - oh the horror! - it's using AI. |
|
There's a new feeling that I experience when using LLMs to do work. It's that every run, every commit has a financial cost (tokens). Claude code can write a nice commit message for me but it will cost me money. Alternatively, I can try to understand and write the message myself.
Perhaps the middle ground is to have the LLM write the classifier and then just use that on the exported bank statements.