balves

Additionally you can annotate a transaction with a "document" tag and that document will show up directly associated in the ui.

The ui has pretty good previewing for these. I add pdf versions of all of my statements, and attach receipts to specific transactions (business expenses, proof of paying taxes, etc.)

It works quite well

If the headline was "California Regional Mutual Bank and Trust fails" (I made up the name, I don't know anything about banking, don't nitpick the terms) it surely would have still been newsworthy because of the size of the bank, but I suspect there would be less vitriol around the situation with the Silicon Valley connotation removed from it.

It depends on the relationship with the person who's code you are reviewing, it depends on the relative seniority differences, it depends on the project, it depends on the rest of the team culture, it depends on the rest of the company culture, it depends on how long you've had a working relationship with this person, it depends on who else might see the review.

I've had working relationships with people where it was beneficial/easier to be super curt and to the point, because there was sufficient 2-sided trust that best interests were at heart. I've had working relationships where I had to take having "open-ended genuine curiosity" to the extreme because of fear of feelings being hurt.

That being said, by default I take a question-asking tone to the code review process, with the intention of possibly learning something. It opens up the door to "being wrong" and allowing things to progress without incessant arguing. There are times when this approach isn't appropriate, but I think it's a reasonable default. Again, it depends.

https://github.com/jbms/beancount-import

https://beancount.github.io/docs/importing_external_data.htm...

Support for OFX is generally great, CSV is also great. There are some proof of concept things floating around too for PDF.

It's VERY hard to accidentally miss capital gains, or get cost basis wrong on something, or have something not balance. Much harder than even ledger-cli, let alone the other alternatives. It feels at times like working with a static type system versus a dynamic type system.

And the burden associated with this is not anything more than other tools. Importers have been great. I have 68 asset subaccounts between my spouse and I (if you do double-entry accounting you'll know this isn't actually that many), and I spend about 1-2 hours a month balancing the books, doing reporting, etc.

Finally, it's quite easy to get your transactions into a pandas datatable or similar, allowing you to utilize your programming/datascience skills to do things that just aren't available in other tools. Mint offers nothing here, spreadsheets can do some of it (but the downsides of accuracy), and gnucash requires learning some niche scheme stuff; it feels very "tacked on".

It seems like it might be a nice way to get reproducible dev environments, without some of the headaches being discussed here.

Is this a common use, or do people typically just do all-or-nothing?