u/Key_Buyer_338

Got a call this morning from a guest who was absolutely livid. He's checking out and sees a $28 club sandwich and two glasses of Chardonnay on his bill that he swears he never ordered.

my first thought is, great, another system glitch or a server punching in the wrong room number. so I go back through the checks. Nope, the order was called in from his room's phone, Room 305, plain as day. The server who took it up remembers it clearly. So I go talk to the guest again, very politely, and show him the timestamped order. He looks at it, and then it dawns on him. "Oh," he says, "my colleague from room 307 was in my room yesterday afternoon for a meeting. He must have ordered it."

I ask if his colleague can cover the bill. And then the punchline: his colleague checked out at 5 AM this morning to catch a flight.

The guy in 305 flat-out refuses to pay for it. Says it wasn't him, and he's not responsible for his colleague's lunch. We went back and forth, but in the end, with him threatening a chargeback on his entire stay and a nasty review, what could I do? I had to comp the meal.

its not the $40 that's killing me. It's the sheer stupidity of the situation and the time wasted. This is the third time in six months something like this has happened. The "charge it to the room" system is built on an honor system that guests are all too happy to exploit.

so today was the final straw. I spent the afternoon putting new little acrylic stands in every room. Each one has a QR code to our online room service menu (we use menuforma for it). From now on, you want food? You scan the code, you order with your phone, and you pay with your own damn credit card right then and there.

We'll probably get some pushback from older guests who miss the old way, but I'm done eating the cost for other people's friends.

If you're learning this and model sizes are confusing you, here's the distinction that matters more than the headline number.

A dense model runs every parameter for every token. A mixture-of-experts model is split into many sub-networks with a router that picks a few per token, so only a fraction actually computes. That gives you two numbers instead of one: total parameters, which mostly sets your memory footprint, and active parameters per token, which mostly sets speed and cost.

This week's release from Ant's lab, Ling 3.0 Tiny, is a clean illustration of how far apart those two can now sit. 7.9B total, about 1.3B active per token. So it carries the knowledge footprint of an 8B model while doing roughly a sixth of the per-token arithmetic.

A caveat worth building into your habits early: those are the vendor's own published figures, and vendor figures are marketing until somebody independent reproduces them. I haven't seen an independent eval. It's also API-only, which means you can't inspect it or run an ablation on it, so it's a poor object to learn from even if it turns out to be a fine one to use.

Does anyone know a genuinely good explanation of the active-versus-total distinction? Everything I find jumps straight into routing maths and skips why a learner should care.