I biked 4,042 km in 2023. 44.1% of that was for recreation; 55.9% was for utility (with 32.0% for my commute). Almost all of this was on my Raleigh Record Ace.
I spent $417.37 on #cycling, including building new bike stands for my office. That's $0.103/km, or $0.185/km if you only count utility cycling. Compare to about $0.40/km driving!
I used #ledgercli to track distances and expenses, and #gnuplot for the graph.
Spent some time wrestling with #cPlusPlus and #debugging in #gdb to give #ledgerCLI the ability to cope with the UK's mad tax year. I blame Henry VIII 👑
I am currently at the 2nd rewrite of my #plaintextaccounting#ledgercli tooling and still find things I don't like/enjoy with this setup.
It's like 200% better than the first iteration though.
Let's hope the time invested will be returned. At least I had to reread the full manpage and online manual so I already learned/remembered some things I already forgot.
I keep flip-flopping between #YNAB for convenient envelope budgeting and #PlainTextAccounting for version-controlled portable data that's fully in my control. I'm considering going (back) to #HLedger (used it for a couple of years, used the original #LedgerCLI even further back) but as I know #python I'm wondering whether to try #beancount in case I want to hack my system further.
Any opinions/experiences with the three plaintext accounting heavyweights? Or tips for making envelope budgeting less painful in this ecosystem?
I've started doing #plaintextaccounting not sure yet if I'll mainly use #ledgercli or #hledger the journal formats are nearly identical so I can keep it mutually compatible for now.
It'll depend on the differences of the formats and the tools, but maybe the tools aimed at ledger-cli will just work anyway?