What Being Ripped Off Taught Me

The setup: a rushed pitch and a quick visa

A friend flagged an opportunity in Spring 2024: a California client allegedly needed help finishing an augmented‑reality bus tour in Beijing. It has been reported that the author — who’d previously consulted on AR bus bids for The Mill and IDEO — flew out immediately on a still‑valid visa, curious to see how the project’s thorny problems had been solved. Curiosity turned to unease on the first call, when the team demurred on technical details. First warning sign? Don’t ignore it.

Chaos on wheels: engineer soup and missing basics

What the author found on arrival was a mess. It has been reported that multiple very junior developers were editing binaries and TouchDesigner patches and deploying to production with thumb drives — no version control, no standards. Cameras were misconfigured, gyroscope axes flipped, GPS flaky, render pipelines re‑rendering 35+ fullscreen layers with alpha hacks, consumer PCs and OLEDs overheating in direct sun, and a “rack” that was an MDF shelf bumping down dirt roads. In plain English: the rig was built by people who’d never been asked to sustain it in the real world. How do you sell high‑end AR and skip basic engineering?

The personal toll: patience, then resignation

The emotional center of this story is the author’s patient, escalating effort: measure lens intrinsics, add color science, get second, stable cameras, rebuild the render pipeline, standardize Windows builds before rolling out to ~20 buses. They begged and begged. But the team, described as carpetbaggers and dilettantes, allegedly shrugged and doubled down — convinced by VJ lore and hubris that they could close gaps solvable only with math and seasoned engineering. The moment of truth? “Fuck around and find out.” Ouch.

A cautionary tale for AR projects

This isn’t just a cautionary anecdote; it’s a checklist. If you’re a client or contractor in AR, ask for version control, test rigs, measured intrinsics, redundancy in sensors, and clear maintenance plans before you green‑light a fleet. Money and hype will get you a prototype. Real deployment demands engineering discipline. Want to avoid being ripped off? Do your due diligence — and when someone says “how hard could it be?”, believe them.

Sources: belief.horse, Hacker News