Overeducated, Ph.D.

Writings, Regrets, and Re-skillings during the AI Revolution

Author: Professor Lamb

  • Before and After Networks 5: Shopping and Banking

    Most transactions used to happen in person, because value could not move without paper or a handshake.

    Before networks, people shopped in physical stores, visited brick-and-mortar banks, and commonly used cash or checks. The bank’s marble lobby was not decoration; it was an argument that your money was safe.

    Now people shop, pay bills, deposit checks, and transfer money online — and they also face scams, hacking, and system outages. The same connection that lets you deposit a check at midnight lets someone on another continent try your password at the same hour.

    Trust migrated from architecture to protocols. Convenience and attack surface scale together — every new thing you can do remotely is a new thing that can be done to you remotely. The trade is worth it, but only if you know you are making it.

  • Before and After Networks 4: Work and School

    Work and school used to be places before they were activities. Participating meant being bodily present.

    Before networks, people worked and learned in offices and classrooms. They relied on printed forms and handouts, and job seekers completed paper applications in person or mailed printed résumés to employers.

    Now people can apply for jobs, work, learn, and collaborate remotely through websites, video meetings, cloud services, and shared documents. I teach sections where I never share a room with my students, and it works.

    The through-line: once work became information flow, it could travel wherever packets travel. Presence stopped being a building and became a connection. That redrew the geography of jobs and education — and it quietly made a reliable connection the new prerequisite for showing up at all.

  • Before and After Networks 3: Communities

    For most of history, relationships were based mainly on physical location. Your community was, almost by definition, the people within walking distance.

    Before networks, relationships developed through families, schools, workplaces, neighborhoods, and local organizations. People were more likely to know their physical neighbors, and businesses reached nearby customers through local newspaper ads.

    Now people form communities with others anywhere in the world — around a hobby, a profession, a rare disease, a very specific joke — although they may interact less with the people on their own street.

    Networks decoupled belonging from proximity. The gain is real: no one with an unusual interest or an unusual condition has to be alone with it anymore. The cost is real too: you can know someone nine time zones away better than the person next door. Both things are true at once, which is what makes this one hard to score as progress or loss.

  • Before and After Networks 2: Knowledge

    Finding information used to require real time and effort. It was an errand — you went somewhere, asked someone, or paid for a shelf of books.

    Before networks, people relied on libraries, card catalogs, expensive encyclopedias, and local experts. An encyclopedia set was a serious household purchase, sold door to door and out of date the day it arrived.

    Now search engines and AI provide information in seconds — but users must decide whether it is accurate and trustworthy. The answer arrives instantly; the judgment still takes as long as it ever did.

    The bottleneck moved from access to verification. The old gatekeepers were slow, but they curated; the network delivers everything, including the nonsense, at the same speed and in the same font. That is why I tell students the real skill is no longer finding an answer. It is deciding which answer deserves belief.

  • Before and After Networks 1: Messages

    ITN 101 is a whole class about computer networks: how they connect, the Internet, Wi-Fi, and the technical skills involved in building and supporting all of the above. It is worth pausing at the beginning of the semester to contemplate how much our daily lives rely upon these networks—and how much society has changed as a result. What would your life look like without them? Do you ever unplug—or is it too intolerable? Over the next ten days, I will work through ten impacts, starting with the most obvious one.

    Communication used to be much slower, often more expensive, and traditional correspondence was usually one-to-one. It could also feel more deliberate.

    Before computer networks and the Internet became part of everyday life, people wrote letters with pen and paper, read printed notices and newspapers, and used landline phones. Long-distance calls were billed by the minute and expensive enough that some families scheduled them in advance and watched the clock while they talked. A printed message to another city could take days; an international letter could take weeks.

    Of course, telephone, radio, and television systems predated computer networking. They were electronic communication networks, not computer networks, but they helped set the stage. Telephone circuit switching, copper wiring, coaxial cable, and radio transmission all contributed technologies or ideas that computer networks later adapted. I’ll return to telephony itself on Day 10 of this series.

    Today, messaging services—including iMessage, RCS, WhatsApp, and countless others—along with email, social media, and video calls make communication nearly instant and inexpensive, even globally. Many modern services are cloud-hosted and designed mobile-first, while users often reach them through Wi-Fi or cellular networks. These services also allow large groups to connect at once. A modern group chat combines immediate conversation, images, video, and a persistent history—capabilities that once required several separate communication systems and much more advance coordination.

    Notice that when the cost of sending one additional message approaches zero, delivery stops being the scarce resource and attention becomes the bottleneck. At the same time, digital communication creates new risks and dangers from (mis)information overload, to privacy and surveillance, to possible digital vulnerabilities of critical infrastructure. As much as we may daydream about life before the Internet, there really is no unwind button for society: we live, work, and play in sociotechnical systems that are heavily internetworked today.

  • The Knot in the Network

    The Knot in the Network

    In Computer Networking, the basic unit of science is the ‘node.’ All computers and chips, anything that sends or receives traffic, is a node. Nodes are connected by links. Networks consist of nodes and links. Some nodes are routers, some are hosts.

    The origin of the word is the Latin nodus, “knot”—the thing you tie in a rope. Trace it further back to its Indo-European root ned-, “to bind or tie,” which also produced Latin nectere, “to bind,” which gives us connect, annex, and nexus; and through the Germanic line it produced the English word net. “Network node” is therefore very nearly a redundancy—the knot of the knotted thing!

    For most of its career the word named distinguished points in continuous things, such as where orbits cross in astronomy. But for Computer Networking, the decisive precedent is electrical. In 1845 Gustav Kirchhoff, still a student at Königsberg, published the two circuit laws every engineering student now learns; the current law—what flows into a junction flows out—is known in German as the Knotenregel, the knot rule, because a junction where conductor branches meet is a Knoten, a knot. Electrical engineering was calling its junctions knots a century before anyone switched a packet.

    Königsberg, fittingly, is also where network mathematics comes from: Leonhard Euler’s 1736 analysis of the city’s seven bridges is the conventional origin of graph theory, the abstraction (a graph = points joined by lines) by which orbits, stems, circuits, and telephone exchanges become the same object. The word graph itself came later, coined by the mathematician James Joseph Sylvester in 1878; mathematicians tend to say vertex, engineers say node, and they mean the same thing.

    Computer networking inherited both lineages at once. Paul Baran’s 1964 RAND studies, On Distributed Communications, asked whether a web of switching nodes with redundant links could survive the loss of many of them. (Spoiler: YES).

    When the ARPANET went live in 1969, its design split the graph world into two: a communication subnet built of Interface Message Processors were called the “nodes,” with UCLA’s IMP as node number one—versus the timesharing computers that actually served users, the “hosts.” That division of labor is why the network’s very first Request for Comments, RFC 1 of April 1969, is titled simply “Host Software.”

    The standards later fixed the usage into law. RFC 8200, the current IPv6 specification, defines a node as a device that implements the protocol, a router as a node that forwards packets not addressed to itself, and a host as any node that is not a router. So in IETF terms every host is a node, and routers are the nodes that aren’t hosts.

    The IEEE, meanwhile, preserves the older topological sense: the 802 LAN standards largely avoid node for end systems, preferring station, while IEEE glossary usage keeps the graph-theoretic meaning — an endpoint of a link, or a junction common to several. The definitions differ because they draw different graphs: to Ethernet, a switch is a node; to IP, the whole switched segment collapses into a single link and the switch vanishes.

    Two thousand years of usage agree on the essential point. To call something a node is to make a relational claim: a node is not a kind of thing but a kind of position. A device becomes a node the moment it is tied into something larger, and ceases to be one the moment it is cut loose. The Romans would have found nothing strange here — a nodus was always a place where separate strands are made to hold. We did not stretch the word to fit our machines; we finally built the thing the word was waiting for.

  • Four Rules for Governing World Models

    Series note. To mark the completion of my ECE 5864 Critical Engineering capstone, I’m publishing a seven-part adaptation for a special week of ITE 135: AI Awareness. These posts are longer and more formal than my usual entries because they began as a graduate research paper. This is Part 7 of 7.

    Critical Engineering Recommendations

    Require independent safety and quality testing before deployment. A world-model robot controller should not be used around workers until an independent evaluator has tested the exact model, robot, task, and factory environment. Testing should include unusual parts, blocked sensors, lighting changes, worker entry into the cell, damaged equipment, and other foreseeable failures. A successful vendor demonstration geared toward marketing and the venture capitalists is not enough. The system should also be retested after major model updates, new training data, or changes to the environment. If the system cannot show safe behavior under these conditions, it should not be used in production environments.

    Protect workers, jobs, and the right to stop the system. Employers should complete a risk and impact assessment before introducing this type of automation. The assessment should estimate jobs lost, jobs changed, wages affected, training needs, and new safety hazards. Workers and their representatives should participate before deployment, not after the purchasing decision has already been made. Factories should have a clearly tested emergency-stop process, and workers should have the authority to halt operation without retaliation. Employers should also fund retraining, continued manual practice, and transition support for workers whose jobs are eliminated or reduced. Productivity gains should not be treated as a complete benefit calculation while job loss and lost wages are externalized by the company.

    Do not count a human monitor as a safety control. The most common industry answer to the risks described above is to place a trained person in a supervisory position and treat that person as the safeguard. The Avride investigation is direct evidence that this does not work. A qualified safety operator occupied the driver’s seat during all sixteen crashes under review, and in only one of them did that operator attempt to intervene. A learned model/agent acts faster than a passive observer can reliably react, and a supervisor watching a system that behaves correctly most of the time will stop watching it closely. Employers and regulators should therefore require that a deployment be safe on its engineered limits alone, e.g., force and speed ceilings, protective stops, physical separation, and restricted task boundaries that hold whether or not anyone intervenes. Where human intervention is still claimed as a mitigation, it should be measured rather than assumed: the assessment must document the time a worker actually needs to detect a fault and stop the machine, verified under realistic conditions rather than during a scheduled test. Supervision should be treated as a way to catch problems and improve the system over time, never as the primary barrier between a machine-learning model and a human body.

    Assign responsibility and blame before an accident. Contracts and regulations should identify which party is responsible for the foundation model, robot integration, safety controls, software updates, and day-to-day operation. Each deployed version should have a model data provenance card that records its origin, training changes, known limits, and safety tests. Serious failures and near misses should be reported to a shared public database so that one company’s accident can prevent another company’s possible fatality. Regulators should also require secure update procedures and checks for compromised model weights because research has shown that generative pipelines can be poisoned through hidden backdoors.

    World models may eventually improve reliability, but that possibility does not justify testing their emerging capabilities on workers in the field as the WEF suggests. Our policy goal should not be to stop world-model research. It should be to prevent companies from shifting the risks of experimental automation onto people who did not design the system and may not share in its profits. Independent benchmarks and quality testing, enforceable worker protections, job-impact planning, public incident reporting, and clear liability laws would require the evidence to catch up with the runaway marketing and hype. Until tech companies and their capitalist advocates can demonstrate that these systems are safe in the real-world physical environments where they will operate, they should not be permitted to gamble with workers’ jobs, property, or lives.

  • The Policy Problem of Physical AI

    Series note. To mark the completion of my ECE 5864 Critical Engineering capstone, I’m publishing a seven-part adaptation for a special week of ITE 135: AI Awareness. These posts are longer and more formal than my usual entries because they began as a graduate research paper. This is Part 6 of 7.

    Introduction and Context

    World models are AI systems that try to predict how the physical world will change. In a factory, that prediction can become a robot action. This makes the technology more dangerous than an ordinary generative AI system. A bad chatbot answer may ‘hallucinate’ or confuse someone. A bad robot command may crush a hand, damage equipment, or kill someone. FLUX-mimic is already being tested at Audi, even though its reliability has not been independently established. The main policy problem is therefore simple: companies are moving experimental AI from video generation into industrial control before workers, regulators, and the public have reliable ways to judge whether it is safe.

    Relevance to Policy and Practice

    Policy action is needed because the costs and benefits will fall on different groups. Audi and its vendors may gain faster production, lower labor costs, and a new market for foundation models. Workers may face injury, job loss, lower wages, or reassignment to monitoring roles with less skill and bargaining power. The safety risk is already real and urgent. NIOSH identified 41 robot-related deaths in the United States between 1992 and 2017, and it warns that unexpected contact, crushing, trapping, and concern about job loss remain important risks as robots work closer to people (CDC 2024). In May 2026, federal regulators opened a defect investigation into Avride, an Uber robotaxi partner operating in Austin and Dallas, after sixteen crashes in which the automated driving system merged into occupied lanes, failed to slow for traffic ahead, and struck objects partly blocking the road (O’Kane 2026). Interestingly, a trained human monitor sat in the driver’s seat for every one of them, and in only a single incident did that monitor attempt to take over. The regulator’s warning about “inappropriate assertiveness and insufficient competence” provokes the very question this report is concerned with: can a world model remain safe at the moment an ordinary reality stops resembling its training data?

    Current world models add another problem: their actions may be difficult to predict and control because the models learn stochastic patterns instead of following a complete set of explicit rules. Symbolic guardrails and explicit prohibitions at some point become necessary again to avoid worst-case statistical blunders. Public stakeholders should have the right to participate in the deliberation and articulation of such absolute prohibitions. These protections remain necessary, but a learned controller raises questions that ordinary guarding and emergency stops cannot answer. Regulators also need to know how the model was trained, how often it fails, what changes after fine-tuning, and whether it behaves safely outside its demonstration data. The NIST AI Risk Management Framework can help organizations identify and manage these risks, but it is voluntary and does not itself prevent an unsafe system from entering a factory (NIST 2023). In short, the current system relies too heavily on vendors and employers to judge their own technology.

    References

    CDC (Centers for Disease Control and Prevention). 2024. “Robotics in the Workplace: An Overview.” National Institute for Occupational Safety and Health, February 9, 2024.

    NIST (National Institute of Standards and Technology). 2023. Artificial Intelligence Risk Management Framework (AI RMF 1.0). NIST AI 100-1. Gaithersburg, MD: National Institute of Standards and Technology.

    O’Kane, Sean. 2026. “Uber Partner Avride Is under Investigation for Self-Driving Crashes.” TechCrunch, May 8, 2026.

  • When a World Model Makes the Wrong Physical Decision

    Series note. To mark the completion of my ECE 5864 Critical Engineering capstone, I’m publishing a seven-part adaptation for a special week of ITE 135: AI Awareness. These posts are longer and more formal than my usual entries because they began as a graduate research paper. This is Part 5 of 7.

    Risks of World Models

    Risks of deploying world models at scale in physical robotics include possible death, injury, and damage. A robot controlled by a world model can make the wrong physical decision, injure or kill a worker, damage equipment, or stop a production line. The same system may also eliminate jobs or reduce workers to monitoring a process they no longer fully understand. These risks are harder to manage because FLUX-mimic is still a vendor-led production test, not an independently validated industrial control system. The critical question is therefore not whether the model can produce convincing demonstrations (it can). It is whether the system is safe, reliable, and accountable when something unexpected happens around real people and machinery.

    The most immediate engineering risk is unreliable behavior. A world model can produce an answer that looks reasonable while being physically wrong (WEF 2026). The literature survey in the Technical Summary section already showed that current video models can generate realistic scenes that fail the fundamental laws of gravity, fluids, and heat (Ding et al. 2025). That problem becomes far more serious when the output is a robot command instead of a video frame. A bad prediction could cause a robot to grip too hard, move into a worker’s space, drop a component, or damage a vehicle. Industrial robots have caused fatal accidents before, especially during maintenance, testing, setup, and other situations when workers enter the robot’s operating area (CDC 2024).

    Another possible risk is job loss. The main economic purpose of this system is to automate assembly work that previously required people. If it succeeds, some repetitive and injury-prone jobs may disappear, but so may stable manufacturing jobs that support workers and communities. The benefits will not be shared automatically. Audi and its technology vendors may gain productivity and lower labor costs while workers face layoffs, reassignment, or pressure to accept lower-skill monitoring roles. Retraining may help some workers, but it is not a complete answer if there are fewer comparable jobs available. Any serious evaluation should therefore count displaced workers and lost wages as costs, not treat them as side effects outside the engineering problem.

    Automation can also weaken human oversight over time. Experienced workers often notice small changes in sound, motion, resistance, or part quality before a formal alarm appears. If people stop performing the task, they may gradually lose the practical knowledge needed to recognize when the robot is behaving dangerously. Supervisors could then become passive monitors of a system they cannot fully inspect or explain. For human oversight to mean anything, workers must retain the authority to stop the robot, receive training on its known failure modes, and regularly practice the manual skills needed to take over safely.

    Finally, the number of supply-chain partners can create a diffusion of irresponsibility effect when a serious failure occurs. Black Forest Labs trained the foundation model FLUX 3, mimic adapts it for robot control via FLUX-mimic, Audi places it on the factory floor, and workers are exposed to the result. If the robot injures someone, each organization may point to another part of the supply chain. Open-weight releases may make this problem worse because many companies can create modified versions with different data, safeguards, and quality controls. Research has also shown that generative pipelines can be deliberately compromised through backdoors and data poisoning (Lapid and Dubin 2025). Clear responsibility, documented model changes, independent safety testing, and incident reporting should therefore be minimum conditions for deployment—not add-ons added after a fatal accident occurs.

    References

    CDC (Centers for Disease Control and Prevention). 2024. “Robotics in the Workplace: An Overview.” National Institute for Occupational Safety and Health, February 9, 2024.

    Ding, Jingtao, Yunke Zhang, Yu Shang, Yuheng Zhang, Zefang Zong, Jie Feng, Yuan Yuan, et al. 2025. “Understanding World or Predicting Future? A Comprehensive Survey of World Models.” ACM Computing Surveys 58 (3): Article 57.

    Lapid, Raz, and Almog Dubin. 2025. “Backdoors in Conditional Diffusion: Threats to Responsible Synthetic Data Pipelines.” AAAI 2026 Workshop on Shaping Responsible Synthetic Data in the Era of Foundation Models.

    WEF (World Economic Forum). 2026. Top 10 Emerging Technologies of 2026. Geneva: World Economic Forum, pp. 29–31 and 47–48.

  • A World Model Enters the Factory

    Series note. To mark the completion of my ECE 5864 Critical Engineering capstone, I’m publishing a seven-part adaptation for a special week of ITE 135: AI Awareness. These posts are longer and more formal than my usual entries because they began as a graduate research paper. This is Part 4 of 7.

    Use Case Description

    For a recent use case analysis, timely as of summer 2026, I chose FLUX-mimic, a new world-model robotic system undergoing production testing at Audi factories for the installation of flexible door seals and the handling of car components in final vehicle assembly (Black Forest Labs 2026b). The system is useful for this report because its learned video-action policy is derived from a multimodal foundation model trained on large-scale video, vision, language, and robotics data rather than being specified entirely through task-specific rules (Black Forest Labs 2026a). That learned policy is only one component of a complete robot-control system that also includes sensors, middleware, action decoding, actuators, conventional software, and safety controls. The relevant engineering question is therefore not whether the model acts alone, but whether the entire robot cell remains safe when the learned component makes an incorrect prediction.

    Black Forest Labs’ wager in its public announcement “Real World Models” is that a generative-AI world model trained to represent reality convincingly must implicitly learn some of reality’s physical regularities, such as how a cable droops or falls, and that this video-learned knowledge can be redirected through transfer learning from pixel generation to motor control. That places the system squarely in the category that the World Economic Forum’s 2026 report describes as world models, alongside the NVIDIA Cosmos platform it highlights (WEF 2026). Adopting Ding et al.’s taxonomy, FLUX-mimic is a future-prediction world model derived partly from generative video AI.

    The main use actors are as follows: Audi’s manufacturing engineers select candidate workflows that have not previously been automated, such as tasks involving floppy or deformable parts, in which geometry is not fixed and strictly repeated motion usually fails. Robotics engineers then fine-tune the pretrained FLUX 3 foundation model into a “video-action model” for each selected task using human demonstrations. The vendors describe this adaptation as requiring only a limited amount of task-specific demonstration data rather than extensive conventional programming (Black Forest Labs 2026b). The adapted model is deployed to a robot cell, where it consumes camera streams and outputs control actions at operational speed. Audi’s process engineers then deploy the cell on the production assembly line, while line technicians supervise operation and handle exceptions. Behind this sequence stands an under-discussed fourth actor: the pretraining pipeline and the broader media economy that supplied its data. Black Forest Labs describes training at massive scale but does not fully disclose the provenance, licensing status, or consent conditions governing that material. This opacity creates unresolved copyright and labor concerns, particularly because the same company sells video generation into film and advertising markets that may disrupt work traditionally performed by human crews and performers.

    Benefits

    The clearest near-term benefit is the automation of physical tasks that conventional industrial robots handle poorly. Traditional systems excel when parts are rigid, locations are fixed, and motions can be repeated exactly; they are far less capable with seals, cables, fabric, food, and other deformable or fragile materials whose shape changes during handling. A world-model controller that predicts those changes could extend automation into final-assembly work that remains manual, repetitive, and ergonomically difficult. In Audi’s use case, successful seal installation could therefore produce both a productivity benefit and a worker-safety benefit by reducing sustained force, awkward posture, and repetitive motion provided that the new robotic system does not introduce greater hazards of its own. A related benefit is faster adaptation and safer experimentation. Conventional automation may require new fixtures, task-specific programming, and extensive validation whenever a product or workflow changes. FLUX-mimic’s vendors claim that its controller can instead be adapted quite quickly compared to traditional robotics (re)programming.

    The possible impact also extends well beyond manufacturing. In transportation, world models could help vehicles anticipate how traffic participants and road conditions may evolve, compare possible maneuvers, and rehearse uncommon emergencies before deployment. In medicine, related predictive models could support treatment planning, medical imaging, surgical rehearsal, or assistive robotics by estimating how a patient or procedure may respond under different interventions. In hazardous-materials handling and disaster response, robots could explore contaminated, explosive, radioactive, or structurally unstable environments while keeping people farther from immediate danger. World models have also been proposed for climate and weather scenarios, scientific modeling, and other systems in which direct experimentation is costly or impossible (Ding et al. 2025). Across these fields, the common benefit is not autonomous “understanding” in the strong sense, but the ability to compare possible futures before choosing an action in the real world.

    References

    Black Forest Labs. 2026a. “FLUX 3 — Real World Models.” Black Forest Labs, July 23, 2026.

    Black Forest Labs. 2026b. “FLUX 3 x mimic: The Next Generation of Video-Action Models.” Black Forest Labs, July 23, 2026.