So there are some things missing from the project…
Issue created…
Implemented and tested…
I also want PDF generation for the invoices…
I did some research and the solution is the correct one.
Ready to implement…
Implemented, now checking the PDF is OK…
All done except code review…
It’s worked but I forgot I need a ‘notes’ field for the invoice and the PDF. Also the PDF is a bit boring looking. I’m going to raise another issue.
Oh, /code-review has come back with some problems…
Fixed…
A few other missing features on the invoices.
All done…
More things I’ve noticed. Should have paid more attention to the original spec and added them there. I guess this happened in normal pre-AI software development as well.
Running the code test suit…
Completed (30 new!)
Code review is amazing!…
Not sure if these things should have been picked up earlier in development and whether a traditional development process would have avoided these earlier in the process.
Being able to set an invoice back to draft after it’s sent so it can be deleted is an obvious error. Currency being global for all sent invoices is another obvious mistake.
I need to check how sent invoices are generated/stored because maybe they should be stored with all the fields permanently saved.
Some this seems to have been over-engineered. I don’t know why it isn’t just storing data in fields in the database and pulling them as necessary. Anyway, seems to be all fixed now.
Oops, not concentrating and didn’t see it wasn’t following the process of first creating an issue before implementing the work. In this case I should have requested multiple tickets for the various missing features and fixes.
Another thing I’m missing that Harvest (app) had. Sortable invoices with filters. Let’s ask Claude Code for this to be added…
Few more changes (headings and totals) and the invoices screen looks like this:
Leave a Reply