I actually use my printers thank you very much. Even bought one of those bank teller slip printer things and a few boxes check-sized slips. I use them for time tracking and todo list.
I didn't go totally crazy, though, and stopped before getting too deep into "...and then OCR them using the check scanner" because I remembered I was already keeping track of start/stop times in a database when printing the slips.
Can you share more about this workflow? I have only recently started to appreciate how my special blend of adhd can work best with there's a physical component to actually _seeing_ the work to be done vs stashed away in a jira, exclusively.
Also... the way I work with it is pretty simple... just three perl scripts... tsta, tpau, and tend. They take a single argument... just a single string I call a tag. Usually something like a jira ticket id, but it could be something more descriptive. Keeps track of it in a sqlite database. The end part moves the record to the archive table, prefixing the start date and time to the tag so I can reuse tags for routine work tasks and that it's also more obvious when I run a report.
Fun fact... the original implementation was in OpenQM, that is, a PICK-style system.
The TL;DR is that it's a physical kanban board mixed with a time clock.
I place them on a ticket rack hanging on the wall above my monitor. It like the ones you see at restaurants... extruded aluminum... filled with marbles... slot on the bottom. If my board is full, I can't (or at least shouldn't) accept more work. It also is an immediate reminder of what needs to be done. The physical process of marking a ticket done and putting it in the finished pile helps to satisfy that need to have a visible sign that work has been done.
In that case... how much is 14 feet of this ticket rack? ;-)
According to https://www.amazon.com/American-Metalcraft-Silver-Aluminum-3... about $180