Control the demo environment so nothing depends on luck

Most demo failures come from the environment, not the code: no internet, an expired API key, a sleeping cloud server, a projector that does not connect. The University of Lahore's Islamabad campus guidelines, for example, make members responsible for arranging their own laptop, internet and project hardware or software, and failures in these arrangements affect the grade.

Before the day:

• Run the system locally if you can, or make sure the hosted version is awake and paid for.
• Prepare seeded demo data so screens are not empty and you are not typing long records live.
• Carry a mobile hotspot and a spare cable or adapter for the projector.
• Turn off notifications, updates and anything that could pop up on screen.
• Test on the actual room's projector or screen if allowed.

On the day, arrive early and run the full demo once before your slot.