You should get a camera and write an OCR scanner that automatically scans the receipts as they are printed, then pushes it into a DB so you can view all your issues via a simple web application, replete with tracking, reminders, and then an e-mail integration that e-mails the opener of the issue when you put a comment on the receipt that's printed and rescanned.
I built a receipt printer for GitHub issues
121–130 of 178 posts
Re: I built a receipt printer for GitHub issues
#122> Wrapping up and next steps The only logical next step here is to get that metal spike thing, so you can stab closed issues on completion.
Re: I built a receipt printer for GitHub issues
#123I also wish there was a metal spike to put closed issues on as mentioned in another comment, lol. Just makes sense.
Re: I built a receipt printer for GitHub issues
#124Re: I built a receipt printer for GitHub issues
#125I would recommend switching to their Events API. Webhooks are great until they aren’t. Querying the Events API means you are able to resume if GitHub, your network or your Raspberry Pi was down. And bonus, your pi doesn’t need to be exposed to the world.
Ooh, that's good to know. I'll keep that in mind for Version 2!
Re: I built a receipt printer for GitHub issues
#126I don't mean to critique the creation, but nobody would bat an eye at an identical solution printing the issues on a normal A4 desktop printer. The lyrical praise and the raving reviews entirely hinge on the gimmicky and "comic" detail of a receipt printer being used instead. Is the hacker community really this under-stimulated?
Also, not speaking for others but I enjoyed it because it's a great example of the hacker mindset and their willingness to write a blogpost to share it with others made my day slightly better.
Re: I built a receipt printer for GitHub issues
#127If you responded to a message with a printer emoji she (Her name was Tilly) would print the message (could even print images/first frame of gifs) in black and white.
Re: I built a receipt printer for GitHub issues
#128You should get a camera and write an OCR scanner that automatically scans the receipts as they are printed, then pushes it into a DB so you can view all your issues via a simple web application, replete with tracking, reminders, and then an e-mail integration that e-mails the opener of the issue when you put a comment on the receipt that's printed and rescanned.
All Hail to the air gapped database - At least no one will be breaking into that one that easily.
Re: I built a receipt printer for GitHub issues
#129Earlier quoted context omitted.
This reminds me of a comment I read a long time ago about somebody's experience working for a company that had a branch in Japan. They would demand that some spreadsheets be sent as a fax, and then some employee would be tasked with re-typing all that information back into a spreadsheet later on.
I once worked at a job where one of the owners of the company, when asked to send a pdf copy of a document, would print out the document on the shared office copier/printer, then scan it back in using the same copier/printer and have it email him the pdf. Every single time he ever made a pdf of any file, even hundreds of pages, he would do this way.
Exasperated, I asked him why he couldn't just send me the raw XML file instead of putting screenshots in a Word document. Turns out the document was on another system he had to remote into (with Citrix, I think? I don't remember what was used back then) and he wasn't "allowed" to copy files off that machine.
Re: I built a receipt printer for GitHub issues
#130There's something about a physical reference to information that you can't quite capture digitally. You can hand it to someone. You can use it as a prop to express your happiness or frustration. You can destroy. I know this was a fun project but I hope we can capture more physical interactions in the future, and not just in VR.
I ended up trolling the system by simply adding post-it notes to post-it notes for subtasks as a protest against the fact that I could never keep any useful detail against them and the tasks themselves ranged between gigantic and functionally unsolvable (it was infrastructure work, so "done" didn't really exist).