Safety Is the Workload, Not the Wrapper
If verification, testing and alignment consume the majority of lab resources, then guardrail-as-a-service framing is architecturally wrong: containment and replay must be runtime subsystems with their own compute budget, not a moderation endpoint bolted onto a model call.
AngleTreat the 80% figure as a budgeting claim and follow it into platform design: what changes in scheduling, sandboxing, replay and cost accounting when verification is the primary workload.
Source video ↗Natural Language Is Not a Compiler
Moving the authoring interface from C++/CUDA to natural language lowers the barrier to entry but removes correctness enforcement from the front end, so the verification burden does not disappear — it moves downstream and gets more expensive per artifact.
AngleCounter the 'lowered barrier means less engineering' reading by tracing where correctness guarantees are re-established once the compiler-style contract is gone.
Source video ↗Where the Constraint Migrates
When a layer of the AI stack saturates, the binding constraint moves down the stack to the hardest-to-substitute layer — from accelerators to power and grid access — so scaling roadmaps should be planned against the lowest layer, not the most talked-about one.
AngleUse Huang's energy claim as the test case for a general rule about planning against the lowest binding layer in layered platform shifts.
Source video ↗Automation Only Expands a Job Where Demand Is Elastic
The radiology case is not evidence that task automation preserves employment in general; it is evidence that it preserves employment where the human bottleneck is throughput-bound and residual demand is elastic — which makes the counter-example conditional, not universal.
AngleReframe the famous counter-example as a boundary-condition result and ask which professions share its elasticity profile.
Source video ↗