Pip: David Nadas went on a cruise and came back with a trip report that is, functionally, a white paper on the future of wearable computing.

Mara: That's the territory we're covering today — how a quarter-sized device is quietly rewriting what a hospitality experience can look like, from the gangway to the casino floor.

Pip: Let's start with the ship itself, and what that little medallion actually does.

The Bleeding Edge of IT is at Sea

Mara: The setup here is a technologist returning from a cruise on the Enchanted Princess and recognizing something he'd been watching since the nineties — RFID, finally deployed at scale in a genuinely unexpected context.

Pip: The quote that anchors the whole piece puts the boarding experience in terms anyone who's sat in a check-in line will feel immediately: "it felt less like a traditional check-in and more like a car passing beneath a high-speed highway toll scanner at 80 mph."

Mara: So the upshot is that friction — the kind that defines most large-ship embarkation — is essentially gone. The Princess Medallion combines Bluetooth Low Energy and NFC RFID in a wearable about the size of a quarter, and the system does the work before you even reach for anything.

Pip: And that frictionlessness compounds across the whole voyage. Your stateroom door unlocks as you walk toward it. Digital billboards in elevator lobbies recognize your Medallion ID and surface photos taken of you onboard. A server on a crowded Lido deck can locate a specific passenger among hundreds of identical lounge chairs to deliver a drink order — no table numbers, no guesswork.

Mara: The security dimension is substantial too. The system maintains a real-time record of who is aboard and precisely where, which effectively neutralizes opportunistic theft and bad actors in a way traditional keycard systems never could.

Pip: There's also a staffing argument buried in here that's easy to miss. When crew aren't managing keycard logistics and manual inventory, their jobs become genuinely more pleasant — and that energy, the post argues, translates directly into service quality.

Mara: The forward-looking section is where it gets speculative. The post describes AI integration that would predictively map passenger behavior, and then goes further — suggesting that temporary, rice-grain-sized RFID chips implanted at embarkation and removed at disembarkation could eventually replace the wearable altogether.

Pip: If you're a recent IT graduate wondering where the real testbeds are, the answer here isn't Silicon Valley — it's the high seas.

Mara: The thread running through all of this is infrastructure that disappears into the experience — technology that works precisely because you stop noticing it.

Pip: Next time, we'll see what else is quietly running in the background. Stay aboard.

Pip: David Nadas asks the question nobody wants answered at brunch: do your vacation photos require a building the size of eight football fields?

Mara: Today we're looking at the infrastructure consequences of how much data humanity generates every day — and what it actually takes to store it. Let's start with the numbers behind every snapshot and scroll.

If your photos need a warehouse, how big is that warehouse?

Pip: The core tension here is a gap between how data feels — weightless, instant, free — and what it physically demands on the ground.

Mara: The post opens with the scale of the problem: "Humanity captures approximately 5 billion to 5.3 billion photos every single day," and once you add sharing and reposting, that climbs to 14 billion images. In data terms, that's 50 petabytes of photos per day.

Pip: And photos are almost the polite part of this story. Video accounts for roughly 82 percent of all global internet traffic, pushing total daily data creation to around 400,000 petabytes — 400 exabytes — every single day.

Mara: To absorb that raw volume without any filtering, you'd need two to three new massive hyperscale data center buildings completed and filled every 24 hours. That's the apocalyptic version of the math.

Pip: The concrete-poured-from-helicopters scenario. Mercifully, the actual answer is more mundane and slightly more reassuring.

Mara: Right — because we delete things. The post puts it plainly: 98 to 98.5 percent of data generated is dropped, compressed, or deleted within seconds or hours. Streaming caches, transient packets, automated logs — gone almost immediately.

Pip: So the real retained-data problem is dramatically smaller. Around 120 to 150 new hyperscale buildings per year, each averaging roughly 400,000 square feet — about eight football fields — against a global stock of 1,200 to 1,300 active facilities today.

Mara: And the post is careful to say the square footage isn't even the hardest part. The real constraint is packing those buildings with denser, higher-capacity drives and securing the electrical grid connections to power them. Moore's Law is still helping on the hardware side.

Pip: Power and grid infrastructure, though, get flagged as the more crucial issue — and deliberately left for a future post. Consider that a cliffhanger with a carbon footprint.

Mara: The closing line lands the point directly back on the reader: slow down on the picture-taking. Do we really need to photograph a parking lot from a train window?

Pip: The uncomfortable answer is that the infrastructure is manageable — it's the grid that isn't, and that conversation is still coming.

Mara: Worth watching for. The physical cost of the digital everyday is a story that's only getting harder to ignore.