I’m a Bev tech, there’s two companies that make bar guns, tapright and multiplex aka wunderbar. There’s more options for fountain dispensing but most of my work is bars and restaurants.
I’d say an app or service that allows restaurants and bars to connect with local independent bar and soda techs to request services. Has the ability to track calls, submit invoices and collect payment along with maybe being able to order from suppliers
There’s alot of places that have no idea who to call for issues relating to that stuff especially with how often staff turns over.
It’s been ages since I worked in a restaurant. IIRC, I never saw that place purge or clean the soda lines. And there was a LOT of plumbing between the fountains and the back where the syrup was kept.
At the risk of making everyone re-think ever eating out again: how often do establishments do that kind of maintenance? And is that within the recommended manufacturer interval?
Most places legit never do unless there’s a problem. When I do service I’ll usually flush what is needed but I don’t have time for a full cleaning since the customer is supposed to do that.
Corporate chains tend to have actual SOP so they tend to be cleaner in general and will have their lines cleaned more often.
I generally suggest every 4 weeks, and to do it when a box needs to be changed since you are only gonna be flushing the last bit of an old box out of the lines. Luke warm water in a 5 gallon pail and you dunk your qcds with the caps off, run the gun or fountain till it’s clear then start mashing the buttons to get any bits stuck in the line. Pull the qcd from bucket then put cap back on, reattach to box and run gun/fountain till product is running properly.
Tbh, it’s not the lines you gotta worry with soda it’s the gun itself, some places never clean the nozzles and they get gross. Also most of the time any bad tastes are related to water or a bad syrup ratio. I had someone call me saying their lemon lime tasted “dirty” it was a bad ratio, took me not even 5 min to fix.
I’d worry more about the beer though that’s a whole different beast. Lines should be done every two weeks, once a month at the very least. That shit will make you sick if it’s dirty enough, I’ve seen so horrid things related to beer.
Fair, though I guess my interpretation was that void* is kind of like a black hole in that anything can fall into it in an unsettling way that loses information about what it was?
Python, on the other hand, deserves all the hate it gets for making whitespace syntactically significant - I even prefer Go’s hamfisted go fmt approach to a forced syntax to python’s bullshit.
Just put them in separate functions. If you have too many levels of indent, your code is convoluted. Sticking to the line length limit sometimes forces you to write more lines than you’d like to. But it makes everything so much more readable that it’s 100% worth the trade off
It’s quite often I have to second guess whether the code is correctly intended or not. Is this line supposed to be part of this if block or should I remove that extra indentation? It’s not always entirely obvious. Extra troublesome during refactors.
In other languages it’s always obvious when a line is incorrectly indented.
Yeah, it is a completely nonsensical thing to complain about. I hate to go around matching curly brackets like some braindead nematode. If you use more than two levels you should rewrite the code in most cases… just use advanced indexing and vectorization (by pythonic ;p). Or you can loop around like a freaking peasent in your inefficient garbage code that nobody can read because it is cluttered with comments explaining basic stuff. There is a reason Python is popular… and it is not because no one can read it. Same goes for dynamic typing - it is a blessing for most tasks. I do not want to explain to the machine what every temporary variables means…
I agree but still you can oftentimes expect that the average person’s initial reaction to be somehow reluctant… until they understand it. it’s like those foods and drinks that you might need to try a couple times before you start enjoying them.
I hate em cos regardless of language auto formatter takes care of everything. So now im typing extra characters and fucking shit up and confusing myself when moving code between scopes.
In all seriousness, I freely admit that I’m biased towards python because it was my first language and remains my favorite. I use an IDE for anything but the simplest scripts, so I’ve very rarely had any issues with spacing.
(Sarcasm/deadpan detected but I’ll respond anyways).
Not when they are visibly the same and the spaces have no other meaning in that context.
Not to mention tabs being annoying in general because of how badly it works to adjust the distance of tab stops. That doesn’t really affect this particular case, but it’s why I generally use spaces instead of tabs.
Most of the annoyance is from vim recognizing that spaces are an error in makefile recipes but still using them unless I copy paste a tab in, including when I hit enter on a line that is using a tab already. It matches the indentation but uses spaces instead of tabs. I’m sure there’s a way to adjust vim config to fix this, but I have yet to acquire the esoteric knowledge required to do so.
OK, that’s excessively “convenient” for booleans. But I don’t get the passionate YAML hate, seems like a simple enough language for config. Didn’t have the pleasure (“pleasure”?) to work with it though, so what’s why else is it shitty?
Do a search for ‘why yaml is bad’ and you’ll get a lot of stories.
Constant passing problems, especially when the yaml gets very large and complex. After I implemented a new feature I was pulled into a call with 12-15 people demanding to know why it didn’t work. The new feature worked fine, The guys yaml had the wrong amount of white space and so it didn’t parse.
White space in the wrong place? Fails Wrong amount of tabs? Fail
Working in a big configuration file that has a lot of nesting? Good luck.
Best part is that most of these things don’t throw errors or anything, it just doesn’t work and you are left scratching your head as to why your deploy only fails in the production environment.
A property can have the wrong indentation and it would still be a syntactically correct yaml. It’s hard to distinguish whether a line is wrongly indented or not. Copy and paste a line and mistakenly use the wrong indentation, and the entire production breaks.
It’s hard to distinguish whether a line is wrongly indented or not.
That’s very much not my experience. I use YAML regularly and while I’ve had copy paste indentation errors when I look at the offending line it’s always obvious to me how to fix the indentation. The only indentation thing that’s ever given me trouble is embedding YAML as a string within a file that uses tabs.
Haskell does both! Most people prefer to use whitespace when writing Haskell but it’s not required. Braces and semicolons are preferred if you’re going to be generating Haskell code.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.