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
81–90 of 178 posts
Re: I built a receipt printer for GitHub issues
#82Re: I built a receipt printer for GitHub issues
#83You 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.
Re: I built a receipt printer for GitHub issues
#84You 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.
Re: I built a receipt printer for GitHub issues
#85There'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.
Re: I built a receipt printer for GitHub issues
#86I 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.
Re: I built a receipt printer for GitHub issues
#87Re: I built a receipt printer for GitHub issues
#88I did end up reusing the printer to turn it into a Game Boy Printer, though! ...And I make sure to only print pictures I plan on keeping. ;)
Re: I built a receipt printer for GitHub issues
#89You 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.
Web 2.0 -> Web 1.0 -> Web 2.0 adapter.
Re: I built a receipt printer for GitHub issues
#90You 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.
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.