Certain workflows prefer non-queueing, for instance the throng empowers the bartender to load balance different groups, delay drinks to over consumers, etc etc. So other cultures can have those workflows in places we might not expect, that is not necessarily a matter of respect. In pub culture, queueing disrespects the bartender.
It depends. Many places in the UK have a tradition of "virtual queuing" at bars; they don't stand in a line because that would usually block the space, but everyone remembers who was before them. Usually the barkeep remembers as well, but sometimes they ask "who's next" and people defer to those ahead. But load balancing also happens.
You're conflating efficiency norms with respect norms. Never mind that the core reason for no queues in bars is space efficiency and historical norms, allowing the bartender to select regulars, better paying customers, etc. without being stressed for time.
But in any case, your edge-cas applies when someone exists to manage the queue. That's not the case for e.g. elevators, self-checkout lanes, DMV lines, or, I'd argue, that vast majority of queues encountered regularly.
It makes a great code reading tool if you use it mindfully. For instance, you can check the integrity of your tests by having it fuzz the implementation and ensure the tests fail and then git checkout to get clean again.
I got mine to bundle all that bs into a one word suffix "DISCLAIMER." which it puts at the end of responses now but basically doesn't bother me with that stuff.
I was staying at a Maasai owned ecolodge in Kenya on the day they switched over from generator to solar. It was so much quieter, and with their new electric Range Rover they don’t ever have to go into town except for parts.
We handle this in Fireproof with a deterministic default algorithm, in addition to having a hash-based tamperproof ledger of changes. Fireproof is not SQL based, it is more like CouchDB or MongoDB, but with cryptographic integrity. Apache 2.0 https://use-fireproof.com
In practice during CouchDB's heyday, with lots of heavy users, the conflict management API almost never mattered, as most people can make do with deterministic merges.
It’d be amazing to see a collab with the Exquisite Creatures Revealed artist. He preserves all kinds of insects and presents them in a way that highlights the color and iridescent effects nature offers. I was so blown away by the exhibit I went back. Artist: https://christophermarley.com/
Yes, that exactly. If you have to read the code or the manual, you’re not vibe coding. I think vibe coding is super good for the industry and people in general.
