454: Workshop design with Aji Slater

What It Covers

Aji Slater explains relational-based access control systems derived from Google's Zanzibar paper, contrasting them with role-based systems, then discusses workshop design principles including pacing strategies, hands-on learning approaches, and catch-up mechanics for participants.

Key Questions Answered

• •Relational Access Control: Uses directed graph data structures where entities connect through relationships, enabling fine-grained permissions for individual items rather than broad role-based rules. Originated from Google's Zanzibar paper for managing complex cross-app permissions in social networks.
• •Workshop Pacing Reality: Workshops cover approximately one-third the content of equivalent talks due to participant typing speed, environment issues, and hands-on time. Plan save points via Git commits every 10-15 minutes so attendees can catch up without derailing the group.
• •Incremental Learning Structure: Design workshops with small feature-based loops where participants learn one concept, implement it to solve a practical problem, commit working code, then move forward. This creates dopamine wins while building knowledge progressively rather than teaching theory upfront.
• •Workshop Catch-Up Mechanics: Provide repository checkpoints at each exercise completion, enable offline text-file alternatives to avoid WiFi dependency, and assign teaching assistants for individualized help. This prevents single participants from blocking entire group progress when encountering local environment problems.