Restaurants typically have fairly low profit margins, so there generally isn't a strong desire to spend limited free cash flow to upgrade/replace a point-of-sale system that's functioning satisfactorily.
Especially since it's not something capable of a significant ROI since the PoS system usually has little-to-no impact on either revenue or profit. A slow one could impact productivity - but this is rarely a bottleneck so in most cases there would be little gained by spending money to upgrade to a newer system.
> I've essentially stopped getting delivery which is a bad sign since I'm basically the target audience
Same, rarely ordered delivery pre-pandemic but then was ordering two or three times a month but eventually got sick of food taking over an hour to arrive from places only a mile or two away so stopped entirely (until discovering a nearby restaurant that does their own delivery and it's great - arrives within 20 or 30 mins and the food is always piping hot).
> the idea of asking people to write code during an interview what sort of revolutionary
And I think it's a great idea, personally I would never consider working anywhere that hired devs without seeing them write some code. But my problem is with the types of questions asked at many companies, specifically the types that require weeks (or months!) of prepping.
During my last job search one interview that stood out (positively) was a problem around parsing some HTTP headers (it started simple and then had layers of complexity added as I solved each one). It was honestly one of the best questions I've seen in an interview as it requires the candidate to be able to write code and solve a problem but without requiring/expecting the candidate to have prepped beforehand to learn (or brush up on) theoretical stuff far removed from the types of problems we actually solve on a daily bases (evidence of this disconnect is demonstrated by the fact people need to prep).
I think this is a great example of the kind of implicit expectations that always pervade these discussions. I had a similar interview in my last job search, and for me it stood out negatively. At the time I’d never parsed any part of an HTTP response in my professional career, so I made some mistakes that look kinda silly if you know what you’re doing, and it was clear that the interviewer didn’t believe me when I explained that this isn’t a problem that comes up often in my field. I don’t want it to sound like I’m complaining, it’s not a big deal, but the interviews a web developer sees as neat and low-prep are exactly the ones I need to prepare extra for.
> Why would anyone be stupid enough to trust google to keep the "ad free" experience ad free?
One can cancel their YouTube Premium subscription at any time for any reason, including and especially if it is no longer delivering an ad-free experience. In the meantime I'm quite happy paying $10 a month (annual plan) to never see ads.
> if you pass in a negative number then that's your own dumb fault if it does something unexpected
If a negative number isn't valid input that should be gracefully handled by the program (e.g. by responding with an appropriate error indicating what is valid and/or invalid) instead of doing something unexpected.
I'm not much of a fan of the current state of tech interviews but seeking clarity around validity of input and how to react to invalid input is one aspect that does (or at least should) mimic "real life"
> People working for tabacco companies have always been in the same boat.
That's not a very fair comparison - there aren't exactly any huge positives associated with tobacco use. So it's not like someone could work for a tobacco company and say "sure some people die from consuming our product but on the other hand look at all the good we're doing..."
That's very different than Facebook where yes there may be some negatives but there's also positives (e.g. it's certainly raised countless millions for various charities, helped people keep in touch with others and discover (or rediscover) relationships, and spread the awareness of important social issues).
The positives you listed are features of most social networks, not just Facebook. If Facebook disappeared overnight, another platform(s), hopefully more ethical, would quickly take over its role, and it could be a net positive for the world.
That seems very optimistic to me. Ethically, Facebook is the perfect exemplar of an internet-oriented company. No better, perhaps, but no worse either because it's such a low bar. It seems at least as likely that any replacement would turn out to be even scummier, simply because it would absolutely have to hire from the same talent pool and would have had even less time to figure out what all the ethical dangers are.
But it's simply not going to happen, so this is all moot.
Yes they would pay, you wouldn't even know the person(s) were conducting an audit. All major hotel chains already do exactly this, typically at least once a year and the property has no idea until weeks later when they get the (very detailed) report.
> I also don't understand the "product-agnostic" part. Isn't k8s a product?
Product-agnostic meaning despite kubernetes.academy being provided by VMware it's not covering Project Pacific[1] or any other specific Kubernetes offering or integration by them or anyone else.
Especially since it's not something capable of a significant ROI since the PoS system usually has little-to-no impact on either revenue or profit. A slow one could impact productivity - but this is rarely a bottleneck so in most cases there would be little gained by spending money to upgrade to a newer system.