Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I built a receipt printer for GitHub issues

aschmelyun.com

Post reply on HN
Print view View original

71–80 of 178 posts

Re: I built a receipt printer for GitHub issues

#71

Post by jasonwatkinspdx »

gotaquestion wrote: post #8

This is a really funny read for a Friday morning. It should play an MP3 of a line cook in a busy diner shouting, "Order up!", and then he can stick it on a rotating order wheel hanging above his desk. EDIT: One of these things: https://www.webstaurantstore.com/choice-stainless-steel-orde...

A friend shared this, and my response then was that the author should go tell his plan to a line cook and see what response he gets :P

For those who haven't been around kitchen culture, it's common to joke about having nightmares about the sound of the ticket printer.

Re: I built a receipt printer for GitHub issues

#72

Post by tristor »

alttab wrote: post #67

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.

This is rather clever satire.

Re: I built a receipt printer for GitHub issues

#73

Post by CameronNemo »

otterley wrote: post #62
CameronNemo wrote: post #47

Earlier quoted context omitted.

I found this in two minutes: https://pubmed.ncbi.nlm.nih.gov/29778011/

Insulin resistance isn't cancer (though I admit it's still troubling).

If you spend more than two minutes looking into it you might find a link to cancer. I don't know. That is just the most concerning research I found in the short time I allotted to the task.

Re: I built a receipt printer for GitHub issues

#74

Post by RankingMember »

AdmiralAsshat wrote: post #60
gotaquestion wrote: post #8

This is a really funny read for a Friday morning. It should play an MP3 of a line cook in a busy diner shouting, "Order up!", and then he can stick it on a rotating order wheel hanging above his desk. EDIT: One of these things: https://www.webstaurantstore.com/choice-stainless-steel-orde...

I'm sure the diner frycook would love to be able to send back every burger order he got with "Closed; won't fix".

"Not a bug...a hair"

Re: I built a receipt printer for GitHub issues

#75

Post by trynewideas »

knute wrote: post #68
ianbicking wrote: post #65

Kind of tangential, but I think it could be a lot of fun to make a "boardgame" computer that has a thermal printer, some number displays, and some buttons. It wouldn't try to run the whole game, but would only assist. It could print out scoresheets or special tokens, roll dice, keep track of a few numbers, that sort of thing. Maybe a barcode/QR scanner so you could round trip, like scan a printout and then choose an…

When I was DMing a D&D campaign I had an idea for using a receipt printer to print a "token" that would represent items that the players acquired and they could keep it or pass it around or turn it back in after it was used or destroyed.

You weren't alone: https://github.com/BigJk/snd

Re: I built a receipt printer for GitHub issues

#76

Post by leipert »

I 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

#78

Post by dev_tty01 »

tevon wrote: post #50

This is awesome, I'd add a QR code with the link to the bottom (if possible on printer). Then could scan with your phone to bring the issue up for immediate triage. I imagine lots of issues can be closed right away (or very quickly).

If it could be closed right away, wouldn't you do that before you print it out? Perhaps I'm a luddite, but wouldn't typing the ticket number into a box almost certainly be faster than getting your phone out, turning it on and scanning the code?

Re: I built a receipt printer for GitHub issues

#79

Post by bob1029 »

leipert wrote: post #76

I 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.

Learned this one the hard way. Events are definitely the way to go. You can guarantee perfect synchronization of state if you use it carefully (i.e. as a log you replay as needed).

Re: I built a receipt printer for GitHub issues

#80

Post by nixpulvis »

tristor wrote: post #72
alttab wrote: post #67

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.

This is rather clever satire.

This is rather clever commentary.
Post reply on HN