The nuclear drone on the drawing board

The idea is from adolescence, drones and flying cars on nuclear power ▸ 0:56, and the style is from an older obsession: a painstaking Blender piece he once made in modernized Da Vinci blueprint style, back when he thought people would buy blueprints of ideas ▸ 2:26. Fed as a reference to Nano Banana Pro, it becomes a design loop: generate the blueprint, hand it to Gemini 3 for engineering critique, apply the corrections, regenerate ▸ 3:22, down to typo triage, the label that read like OmegaWs becoming kilowatts ▸ 4:06.

Two machines come off the board. Version one is honest physics: a gas-heated turbine core with sixty days of autonomy ▸ 8:36, doomed by its own safety, the shielding is so heavy the thing is “una bomba andante” better suited to a NASA rover than anything that flies ▸ 8:49. Version two invokes the permitted cheat, assume the obtainium: an isomer-fuel battery, hafnium-178 triggered by an X-ray, gamma emission converted directly to electricity, no turbine, no boiler, no crushing shield ▸ 5:51, the class of power source you’d need for Nick Fury’s carrier ▸ 7:22. The disclaimers ride along: one lab claimed the effect, others couldn’t replicate it, and he hasn’t studied it deeply ▸ 11:02.

ciencia ficción con reglas: se permite un obtainium, todo lo demás debe cuadrar →

What the entry actually documents is the tooling shift. People are feeding entire papers to the image model and asking for the diagram ▸ 4:30; a childhood fantasy became a coherent, critiqued, typo-checked technical artifact in an afternoon of conversation. His LinkedIn post that night says the quiet part: it keeps getting easier to move an idea from your head to something physical enough to share ▸ 11:26. The bottleneck retreats again, from drawing skill to imagination, the same migration the code already made…