Exactly. And I wouldn't threaten the chargeback. If they refuse the refund or ignore you, then just file a chargeback.
To me, ideally the end result is a chargeback instead a customer support refund. Otherwise they have no incentive to change. A high chargeback percentage could be that incentive.
I think the credit card companies expect you to attempt to talk it out with the merchant first though, so you'd still want to reach out to customer support first to "give them a chance".
That's fair and the practices here do allow for immediate chargeback in my book. My suggestion for reaching out to support comes mostly from being on the other end of chargebacks and being frustrated when that's the first/only tool people reach for.
Chargebacks don't tell the full story, telling support "Hey you told me to pay $5 to see my pictures but there were no pictures. Give me my money or I'll file a chargeback" has a better chance of making it up the chain and changing policy. A chargeback on its own could mean any number of things and it's easier for management to write it off a "just fraud" or similar.
If you just want to screw the company but potentially not encourage them to change = Immediate chargeback
If you want to try and change the company's policies = Support + Chargeback if not fixed
I'm not making a judgement call either way, I think both are acceptable in this scenario. I'm just pointing out that if change is your real desire, the support route has better odds.
Gotcha, I may have made some assumptions on how the process works. From the handful of chargeback stories I've heard from merchants, the credit card company passed along the cardholder's reasoning to the merchant when issuing the chargeback. So the merchant was able to figure out why the customer was unhappy. But that's anecdotal, I don't actually know if that's standard.
The chargebacks I've received all just have a very generic category [0]. I've never see free-form text entry reasons that would allow the customer to explain the "why". Maybe their bank asks them for that info but it's not passed along.
What if you used port knocking, but instead of opening a closed port on a correct knock sequence, you switch the service listening to the target port from honeypot mode to normal mode? Anyone connecting and presenting genuine authorization credentials during that window gets genuine access, while everyone else gets routed to the honeypot.
The 40th basement door from the left opens to a storage closet until someone says, "swordfish" at the 30th door from the left, then 15 seconds later, it opens to a vestibule with an imposing, riveted-iron door for the next 60 seconds. That locked door requires a genuine invitation to admit you to the speakeasy.
If you didn't know the speakeasy was there, you might not bother trying to dig through the back wall of the closet with a pickaxe. If you watched someone else go in, and copied their actions, you still don't have the invitation. Any noise you make banging around trying to fool the automated bouncer is much more noticeable when all the casual traffic and robot-driven attackers are mostly just stealing boxes of detergent out of the decoy closet.
The concern I usually hear is not around the learning to program aspect. Instead, it's that fact that almost every other entry-level programmer is a college grad, and that hiring processes will be biased against older candidates.
A friend is a cook who says that even at decent restaurants, cooks don't get paid much and they get just a minimal share of tips. So when I get takeout, I tip 10-20% and say "Thank-you, here's something for the kitchen." Sometimes I get thanks in return, sometimes just a sour look from a server who expected something more for putting my order in a bag. I have no idea what they'll do with the cash, but hopefully some of it gets to the back of the house.
The cash aspect was incidental. "Front of the house" workers here net a significantly higher take-home because they are the ones receiving the tips and what they pass on to others is typically discretionary. Even many of the best establishments will pay cooks subsistence wages. A few restaurants are going tipless, raising prices slightly and discouraging tips, so they can distribute pay more equitably, but then they can have problems retaining wait staff.
This was my understanding as well. If they just ring up the total and pass you food, there's no expectation of a tip.
I do tip from time to time at places where I'm a regular customer. If I get takeout somewhere near work of home ~4 times a month I'll drop a dollar in once every couple of trips.
It's not normal to tip for takeout, but if you want to, 10% is the standard tip as opposed to 15% for table service. But again, a takeout tip is not expected, especially for a simple order.
To me, ideally the end result is a chargeback instead a customer support refund. Otherwise they have no incentive to change. A high chargeback percentage could be that incentive.
I think the credit card companies expect you to attempt to talk it out with the merchant first though, so you'd still want to reach out to customer support first to "give them a chance".