Strange architecture. They clearly have a queue, but instead of checking previous request, they create a new one. It's like they managed to get the worst of pub/sub and task queue.
No, not that kind of queue. I believe the queue in question is simply the in-memory queue of HTTP requests being processed on each instance, it's neither persisted nor shared between instances.
If an instance is stuck and not replying in time, you make a retry and the new request hopefully will be dispatched to another instance.
Unless you happen to be a dairy farmer -- when I was a kid and we went to my grandfather's farm, he'd draw a pitcher of milk right from the holding tank and put it in the 'fridge for drinking. I'm not old enough to remember drinking it, but my older sister said it tasted better than store bought.
Yeah, I source my ledger from multiple places like bank transactions, investments accounts, cash transactions etc.
I can't really think of a case where I have made a mistake, but if, for example, I sold something to a friend I would debit (+) their "reimbursement" account with the amount they owe me. If I typoed that to 10x the amount, I would just go and correct the typo, I wouldn't make two new entries to revert then correct the mistake.
Not trying to nitpick here, but '2' is not an int here. It's the constant evaluated at compile time. But yeah, valid case if users of your code are in the habit of typing magic numbers into your function that expects enum.
My understanding is that on a practical level, these kinds of issues arise from misusing types (or not caring about them) and naively putting variables of one type into the function that expects another. Examples with number constants typed in manually do not hold ground.
I find the Sharpmaker great for touching up an edge, but not nearly aggressive enough (without adding an aftermarket set of diamond rods) for repairing or setting a new edge
I don't care if you are a fifteenth generation swordmaker who practiced for sixty years...you cannot hold a blade in your hands steadily, at sub-mm precision, for more than one stroke
changing the angle even slightly is effectively starting over
but if you must go old school - BELGIAN COTICULE...all other sharpening stones are inferior, it is no contest imho
>> you cannot hold a blade in your hands steadily, at sub-mm precision, for more than one stroke
That's what the guiding rails are for... So far whetstones with guiding rails are the best sharpening method I found. As you can see from my other comment in this sub-thread, I find Spyderco lacking.
Laser printers have parts that can get very hot. If their "baking" reflowed the parts, but just barely, maybe those hot parts would just cause the exact same problem all over again.
