A walk through the website-creation conversation that started in the After Hours room on NAB Sunday — plus the other technical threads that filled the rest of the night.
By the time the convention floor closed, the After Hours room had picked up its second wind. The conversation kept circling back to one thing: how cheap, fast, and unreasonable it has gotten to build real working software in an afternoon — and what that means for everyone with a Google sheet full of gear, a YouTube channel, or a workflow that doesn’t quite exist yet.
Three different stories about building software the new way surfaced over the day. None of them were the same person, and that was the point: it’s no longer one wizard in the corner. It’s the room.
Asked what was on his second screen, an after-hours panelist shrugged and said it was “just an app I put together with cloud code — I call it Gear Ops.” He had fed it a Google-sheet dump of all his equipment, IP addresses included; the app listed everything by category, pinged each device to confirm it was online, and gave him a one-click browse button that opened the device’s admin page in a browser.
Why it landed: anyone in a control room knows the moment when a camera needs a tweak and the answer to “what was that IP again?” is a sticky note on the back of a monitor. Solving it once, in code, took an evening.
He was planning to show it off at the AI meetup on Friday night.
The morning’s funding conversation took a hard turn into engineering when one of the OHG developers walked the room through a months-long project: a panelist-pages system that turns each crew member’s gear list into a single, deduplicated affiliate catalogue.
The flow he described:
pending queue; a human approves image + description + link before they fan out to every panelist’s page.The build was Claude in the editor + Vercel for deploy + Supabase as the back end. He estimated the AI spend at a few dollars to generate hundreds of catalog pages. The repo started out private — “everything I put up has only ever been for me, so I always make it private” — and is being prepared for public so the community can extend it. That move triggered a careful key audit before the visibility flip (more on that in Part Two).
Ed Dawson of CG Pro, presenting in the Creator Lab to the After Hours feed, made the same case from a 20-year software-engineer’s perspective. His framing:
“Being able to look at a piece of software you’re using right now — let’s say Premiere — see something that doesn’t exist, and in real time build a plugin and drop it in… that’s wild to this code monkey.”
He paired the demo with a sober coda: the engineering mindset still matters. Vibing up a prototype is one thing; understanding how the architecture under it actually fits together is what keeps the thing alive past day three. His pragmatic advice: dig into what the AI built for you, and decide whether it made good decisions.
He also mentioned rebuilding what a former personal assistant used to do, in a day, using AI plus an automation layer (an n8n-style glue framework). Faster, more consistent, no inbox triage.
None of these were demos of a finished product. They were people describing what they had built this month, in evenings, between shows. A control-room utility, a community affiliate engine, a Premiere plugin that didn’t exist that morning. The common stack was small: a code-aware AI in the loop, a hosted runtime (Vercel or local), a Git repo, and the discipline to audit keys before going public.
While the main stage cycled through gear advice and grant strategy, the back channel on After Hours wandered into seven or eight different rabbit holes. The notable ones:
Mid-morning, a remote attendee in Wisconsin flagged a freshly announced Vercel security incident, with the public-service reminder: if you have keys hosted on Vercel, rotate them now — and rotate any GitHub tokens connected to it.
The room responded with a useful self-audit pattern, particularly relevant if you’re about to flip a private repo to public:
.env.One of the more striking demos: a plugin that brings the Comfy UI node graph into Unreal Engine, on top of Cesium tiles streaming Google-Earth-style 3D context. You can frame a camera anywhere on the planet, then let a local generative model retexture the scene photorealistically — without anything leaving the laptop.
The plugin was built by a recently-ex-Epic engineer named Michael; it was posted to GitHub a few days earlier and announced on LinkedIn. The companion plugin from an earlier demo (using Nano Banana to retool camera context) was called Ugen.
The same talk demoed a fully local image-generation pipeline running on a single laptop — a deliberate choice given the conference Wi-Fi. Models referenced:
The forward-looking take from the room: the cloud will always have more compute, but local has crossed the threshold of useful for production, and the trajectory only points one way.
One of those short evening detours that earns its keep. Someone asked what flask, gunicorn, and nginx actually were and how they relate. The answer that landed:
“Flask is to Python what a hand-rolled cigarette is to a vape. Fewer parts. You choose what goes in. It works the same way it always has.”
The three-piece breakdown:
Three pieces, each doing one thing — and a useful mental model for anyone who’s been staring at gunicorn -b 127.0.0.1:8903 in a tutorial without quite knowing what each layer was for.
A Saturday audio-sync glitch during the show was traced back to vMix being overtaxed at 1440p60. The room-shared rule of thumb: watch render-time per frame; you need to remain < 16 ms. Saturday opened in the 12–14 ms range and drifted into the 20 ms range — every frame past 16 ms eats into the buffer until sync slips and frames drop.
An eight-week order delay on an M3 Ultra Mac Studio led to a buying-cycle dive. The Mac Rumors buying-guide framing was cited (last release March 2025, average cycle 547 days, currently at day 410+). One panelist summarized the Bloomberg/Mark Gurman read of a possible October refresh, attributed to component-supply pressure across the industry.
The room’s consensus on now or wait: if it’s a money-making machine, buy it; the 14-day return window at the Apple Store gives you a real-world load-test escape hatch.
A panelist who recently moved to a rural property reported Starlink had been “rarely a noticeable hiccup” for daily Zoom hosting. The one operational gotcha worth knowing: the dish takes firmware updates on its own schedule (somewhere between 02:00 and 04:00 in his time zone) and reboots without asking. Unlike Windows or macOS, you can’t defer it. Pick a time-window setting that matches when you’re definitely not on a stream.
The shape of the day, looked at from the back of the room: every conversation kept arriving at the same shoreline. Smaller teams, faster feedback loops, more capability per laptop, fewer reasons to wait for someone else to build the thing you need. The After Hours version of that was less triumphant and more matter-of-fact: here’s the gear app I built last night, here’s the security note from this morning, here’s the three-line stack you’ve been quietly running for years.
That’s the room. That’s the party.