Building a Custom Sticker Vending Machine
🔗 **Source:** [Building a Custom Sticker Vending Machine](https://www.youtube.com/watch?v=LeKG27vfRCs)
> [!note]+ Document Notes
> tags: [hardware, devrel, developer-advocacy]
> author: Nick
> source: YouTube
> reference: https://www.youtube.com/watch?v=LeKG27vfRCs
> date created: 2024-12-28 19:30
>
> # 🏷️ Title: Building a custom sticker vending machine
>
<!-- deep-read:sections start -->
## 🧰 Action Inbox
- [H1] Prototype with cardboard first before laser cutting/3D printing — 09:23 #hardware
- [H2] Bring backup Wi-Fi and power strips for demos — 26:45 #devrel
- [H3] Create admin/debug controls for live demo management — 30:15 #demo
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- [Viam Platform](https://viam.com)
- [DevCon Conference](https://devcon.org)
## 📝 Summary
- Nick from Viam demonstrates how to build a custom sticker vending machine using Raspberry Pi, servos, and web technologies
- Why it matters: Shows how physical demos create more engagement than traditional slide presentations at developer conferences
- Key stakeholders: Developer advocates, conference exhibitors, hardware enthusiasts
- Risks and tradeoffs: Hardware demos require backup plans, debugging capabilities, and higher costs than software demos
- Bottom line: Interactive hardware demos drive better developer engagement and booth traffic at conferences
## 📖 Main Content
The presentation covers building compelling physical demos for developer conferences, using a sticker vending machine as the primary example. Nick explains the "cheeseburger marketing" approach - starting with something fun and engaging (the demo), revealing technical details (the meat), and ending with a call to action.
The sticker vending machine uses servos controlled by a Raspberry Pi through a servo controller board. Users complete a personality quiz on a touchscreen interface built with TypeScript and Three.js, which then dispenses personalized stickers. The hardware control requires only about 10 lines of code, while most development effort went into the interactive quiz interface.
Technical components include: Raspberry Pi 4, servo motors, servo controller board, touchscreen display, laser-cut enclosure, and 3D-printed servo mounts. Total cost is under $200. The system runs Viam server for hardware abstraction and can operate offline once configured.
## 🗒️ Notes
#### ⏱️ [00:00](https://www.youtube.com/watch?v=LeKG27vfRCs?t=0) — [H1] Introduction and audience assessment
- Key idea: Gauging hardware experience and conference demo exposure
- Evidence: "Who here has worked with hardware before? Who has seen the sticker vending machine?"
#### ⏱️ [02:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=135) — [H2] Viam platform overview
- Key idea: Hardware platform for connecting software engineers to robotics
- Evidence: "Single place for building, deploying, and managing robots from anywhere in the world"
#### ⏱️ [04:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=270) — [H2] Confetti cannon inspiration story
- Key idea: Jim Bennett's Flutter SDK demo using confetti for booth engagement
- Evidence: "It's tough to get attention in an expo hall... how do you cut through that noise?"
#### ⏱️ [07:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=465) — [H1] Psychology of physical demos
- Key idea: Tactile learning creates stronger engagement than visual/auditory only
- Evidence: "People learn by doing and not just by seeing and hearing"
#### ⏱️ [09:23](https://www.youtube.com/watch?v=LeKG27vfRCs?t=563) — [H2] Cheeseburger marketing strategy
- Key idea: Fun engagement → technical details → call to action structure
- Evidence: "Start with something fun, engaging... leads into technical details... call to action"
#### ⏱️ [11:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=675) — [H3] Demo development guidelines
- Key idea: Start with quickest prototype, iterate based on feedback
- Evidence: "Quickest thing you can prototype and prove the idea and then iterate from there"
#### ⏱️ [13:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=810) — [H1] Sticker machine technical architecture
- Key idea: Servos with wire coils controlled by Raspberry Pi through servo board
- Evidence: "Basic movement of how this vending machine works... wire coiled around a servo"
#### ⏱️ [16:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1005) — [H2] Hardware components and wiring
- Key idea: Simple wiring with no soldering required, color-coded for maintenance
- Evidence: "Four wires that go into the Raspberry Pi... no soldering required"
#### ⏱️ [18:20](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1100) — [H3] Cardboard prototyping approach
- Key idea: Start with cardboard before investing in laser cutting or 3D printing
- Evidence: "Cardboard prototyping is fantastic... allows you to iterate very quickly on the idea"
#### ⏱️ [20:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1215) — [H2] Web interface development
- Key idea: TypeScript app with Three.js animations, 10 lines for hardware control
- Evidence: "Code to actually control the hardware was about 10 lines. The rest was building the quiz"
#### ⏱️ [22:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1350) — [H3] Integration and customization options
- Key idea: WebRTC communication enables integration with any web service
- Evidence: "You can start to integrate... custom quiz, web hooks, launch cloud servers"
#### ⏱️ [26:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1605) — [H1] Demo deployment best practices
- Key idea: Bring backup Wi-Fi, power strips, spare parts, and debug controls
- Evidence: "Bring your own Wi-Fi... power strips... administration and debug controls"
#### ⏱️ [30:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1815) — [H2] Live demonstration and debugging
- Key idea: Real-time hardware control through web interface for troubleshooting
- Evidence: "Admin dashboard to dispense stickers on demand... VNC into the Pi"
#### ⏱️ [35:00](https://www.youtube.com/watch?v=LeKG27vfRCs?t=2100) — [H3] Cost breakdown and accessibility
- Key idea: Total project cost under $200 with free software platform
- Evidence: "Raspberry Pi $40-50, display $100, servos pack of 12 for $10"
## 📚 References
- [Viam Platform](https://viam.com)
- [Jim Bennett's Confetti Cannon Blog](https://jimbobbennett.io)
- [Viam Code Labs](https://docs.viam.com/tutorials/)
- [Viam Discord Community](https://discord.gg/viam)
## 🗣️ Paraphrase
- Physical demos create more memorable experiences than slide presentations by enabling tactile learning and direct interaction with technology
- The sticker vending machine demonstrates how simple hardware (servos, Raspberry Pi) can create compelling conference demos that attract crowds and generate engagement
- Success requires careful planning including backup systems, debug tools, and graceful degradation when things go wrong during live demonstrations
## 📰 Newsletter
**Build Hardware Demos That Actually Engage Developers**
Tired of your conference booth blending into the background? Nick from Viam shows how a custom sticker vending machine became the buzziest booth demo, combining Raspberry Pi hardware with web technologies to create memorable developer experiences.
The key insight: "cheeseburger marketing" - start with something fun and tactile, reveal the technical implementation, then provide clear next steps. Physical interaction beats passive observation every time.
**Quick Start**: Begin with cardboard prototypes, bring backup Wi-Fi and spare parts, and always include admin controls for live debugging. Total cost under $200 for a crowd-drawing demo.
Resources: [Viam Platform](https://viam.com), [Hardware Tutorials](https://docs.viam.com/tutorials/), [Discord Community](https://discord.gg/viam)
## ✅ Action Items
#### DevRel
- Developer advocacy: Create tactile demos that enable hands-on learning experiences rather than passive presentations
- Education: Document full build processes including troubleshooting and deployment considerations
- Developer experience: Provide clear hardware abstraction layers that reduce complexity for software engineers
- Developer marketing: Implement "cheeseburger marketing" - fun engagement leading to technical education and clear CTAs
- Community management: Maintain active Discord/forums for real-time hardware troubleshooting support
#### Hardware
- Prototyping: Start with cardboard mockups before investing in laser cutting or 3D printing
- Components: Source reliable servo motors, Raspberry Pi systems, and breakout boards for scalable demos
- Integration: Use platforms like Viam for hardware abstraction and cloud connectivity
- Testing: Build comprehensive backup systems including spare parts, alternative power, and debug interfaces
- Documentation: Create detailed wiring diagrams, cost breakdowns, and assembly instructions
#### Conference Strategy
- Booth planning: Design interactive experiences that create crowds and social media moments
- Technical setup: Bring independent Wi-Fi, power distribution, and remote monitoring capabilities
- Engagement measurement: Track demo interactions, social shares, and post-event follow-through
- Scalability: Design demos that can be replicated by field teams without extensive hardware knowledge
- Content creation: Document build process for blog posts, videos, and community sharing
## 🧪 Hypotheses
- Physical interaction with demos creates stronger memory formation and brand recall than visual presentations alone
- Developers are more likely to try new platforms when they can immediately see cause-and-effect relationships in hardware
- Conference booth traffic increases significantly when crowds gather around interactive physical demonstrations
- Hardware demos with simple, documented architectures generate more community adoption than complex proprietary systems
### 📊 Methodology
- A/B test booth engagement between traditional slide demos and interactive hardware demonstrations
- Survey attendees on recall and likelihood to try platforms 30 days after different demo types
- Measure social media engagement and user-generated content from hardware demos vs. software demos
### ❓ Questions
- How do hardware demo costs compare to increased booth engagement and conversion rates?
- What minimum hardware complexity is required to create meaningful tactile learning experiences?
- How can hardware demos be made accessible to developers with varying physical abilities?
### 🔮 Future Research
- Investigation into optimal demo complexity vs. engagement curve for different developer audiences
- Study of hardware demo effectiveness across different cultural contexts and conference types
- Research on remote/virtual alternatives that maintain tactile learning benefits
### 💡 Implications
- Practice: DevRel teams should budget for hardware prototyping and demo transportation logistics
- Policy: Conference organizers need clearer guidelines for power, networking, and space requirements for hardware demos
- Security: Hardware demos require additional security considerations for device management and network isolation
- Education: Developer education programs should incorporate more hands-on hardware components
- Funding: Hardware demo ROI measurement requires new metrics beyond traditional software engagement tracking
### 🧠 Learning Styles Assessment
Reading level estimate: Flesch-Kincaid Grade Level 8
#### 👀 Visual learners
- Present: Hardware diagrams, wiring schematics, component photos, live demonstration
- Improve: More step-by-step visual assembly guides, component identification diagrams
#### 🔊 Aural learners
- Present: Live presentation with detailed verbal explanation of each component
- Improve: Accompanying podcast episode breaking down hardware concepts for beginners
#### 🗣️ Verbal learners
- Present: Clear definitions of technical terms, analogies to familiar concepts
- Improve: Glossary of hardware terminology, comparison tables between different approaches
#### 🧩 Kinesthetic learners
- Present: Hands-on demonstration, physical components to examine
- Improve: Take-apart kits for audiences to assemble/disassemble during presentation
#### 🧠 Logical learners
- Present: Step-by-step build process, cost breakdown, troubleshooting decision trees
- Improve: Flowcharts for component selection, performance comparison matrices
#### 🧑🤝🧑 Social learners
- Present: Q&A session, community Discord mentioned for ongoing support
- Improve: Breakout sessions for collaborative hardware building, peer code review
#### 🧘♀️ Solitary learners
- Present: Complete documentation for independent building, GitHub repositories
- Improve: Self-assessment quizzes, individual project idea generators
#### 🌿 Naturalistic learners
- Present: Discussion of recycling cardboard for prototypes
- Improve: Analysis of electronic waste considerations, sustainable hardware choices
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Clear verbal descriptions of hardware components and connections
- Improve: Detailed alt text for all diagrams, tactile description of physical components
#### Keyboard navigation
- Present: Web interface can be controlled via keyboard
- Improve: Voice control options for hands-free hardware interaction
#### Contrast and readability
- Present: High contrast display on touchscreen interface
- Improve: Adjustable text size options, dark mode for quiz interface
#### Text resizing and reflow
- Present: Responsive web interface adapts to different screen sizes
- Improve: Testing at 200% zoom, ensuring button targets remain accessible
#### Media and captions
- Present: Live demonstration with simultaneous verbal explanation
- Improve: Auto-generated captions for any recorded demo videos
#### Forms and interactions
- Present: Large touch targets for quiz interface, clear success/failure states
- Improve: Alternative input methods for users unable to use touchscreen
#### Standards reference
- Quiz interface should meet WCAG 2.2 AA standards for interactive content
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Universal appeal of personality quizzes, hardware concepts
- Improve: Localized quiz questions that work across cultural contexts
#### Inclusive language
- Present: Gender-neutral language in quiz options and technical documentation
- Improve: Avoid cultural idioms in international documentation
#### Neurodiversity support
- Present: Clear step-by-step instructions, consistent interface structure
- Improve: Options for reducing visual animations, simplified alternative interfaces
#### Representation
- Present: Focus on technical merit rather than personal demographics
- Improve: Showcase diverse community projects built with similar approaches
#### Psychological safety
- Present: Encouraging tone about learning from mistakes and iteration
- Improve: Explicit statements about beginner-friendliness, no judgment zones
### ✅ Logical Validity
#### Strong reasoning
- Deductive strength: Physical interaction enhances learning → hardware demos improve engagement
- Inductive strength: Multiple examples (confetti cannon, sticker machine) support engagement thesis
- Causal reasoning: Crowd formation creates positive feedback loop for booth traffic
- Analogical strength: Comparison to street performers gathering crowds effectively illustrates principle
#### Fallacies
- Appeal to novelty: Assumes newer/physical demos are automatically better without considering context
- Survivorship bias: Only shows successful hardware demos, not failed attempts or contexts where they don't work
#### Tone of voice
- Overall tone: Enthusiastic and encouraging while being realistic about challenges and preparation needed
### 🛡️ DARVO Analysis
- Deny: No significant denial patterns observed
- Attack: No attacks on traditional demo approaches, constructive criticism only
- Reverse victim/offender: No victim/offender dynamics
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Building a Custom Sticker Vending Machine|Full Document Contents]]
## Document Notes
---
tags: #hardware #devrel #developer-advocacy
author: Nick
source: YouTube
reference: https://www.youtube.com/watch?v=LeKG27vfRCs
date created: 2024-12-28 19:30
---
# 🏷️ Title: Building a custom sticker vending machine
## 🧰 Action Inbox
- [H1] Prototype with cardboard first before laser cutting/3D printing — 09:23 #hardware
- [H2] Bring backup Wi-Fi and power strips for demos — 26:45 #devrel
- [H3] Create admin/debug controls for live demo management — 30:15 #demo
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- [Viam Platform](https://viam.com)
- [DevCon Conference](https://devcon.org)
## 📝 Summary
- Nick from Viam demonstrates how to build a custom sticker vending machine using Raspberry Pi, servos, and web technologies
- Why it matters: Shows how physical demos create more engagement than traditional slide presentations at developer conferences
- Key stakeholders: Developer advocates, conference exhibitors, hardware enthusiasts
- Risks and tradeoffs: Hardware demos require backup plans, debugging capabilities, and higher costs than software demos
- Bottom line: Interactive hardware demos drive better developer engagement and booth traffic at conferences
## 📖 Main Content
The presentation covers building compelling physical demos for developer conferences, using a sticker vending machine as the primary example. Nick explains the "cheeseburger marketing" approach - starting with something fun and engaging (the demo), revealing technical details (the meat), and ending with a call to action.
The sticker vending machine uses servos controlled by a Raspberry Pi through a servo controller board. Users complete a personality quiz on a touchscreen interface built with TypeScript and Three.js, which then dispenses personalized stickers. The hardware control requires only about 10 lines of code, while most development effort went into the interactive quiz interface.
Technical components include: Raspberry Pi 4, servo motors, servo controller board, touchscreen display, laser-cut enclosure, and 3D-printed servo mounts. Total cost is under $200. The system runs Viam server for hardware abstraction and can operate offline once configured.
## 🗒️ Notes
#### ⏱️ [00:00](https://www.youtube.com/watch?v=LeKG27vfRCs?t=0) — [H1] Introduction and audience assessment
- Key idea: Gauging hardware experience and conference demo exposure
- Evidence: "Who here has worked with hardware before? Who has seen the sticker vending machine?"
#### ⏱️ [02:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=135) — [H2] Viam platform overview
- Key idea: Hardware platform for connecting software engineers to robotics
- Evidence: "Single place for building, deploying, and managing robots from anywhere in the world"
#### ⏱️ [04:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=270) — [H2] Confetti cannon inspiration story
- Key idea: Jim Bennett's Flutter SDK demo using confetti for booth engagement
- Evidence: "It's tough to get attention in an expo hall... how do you cut through that noise?"
#### ⏱️ [07:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=465) — [H1] Psychology of physical demos
- Key idea: Tactile learning creates stronger engagement than visual/auditory only
- Evidence: "People learn by doing and not just by seeing and hearing"
#### ⏱️ [09:23](https://www.youtube.com/watch?v=LeKG27vfRCs?t=563) — [H2] Cheeseburger marketing strategy
- Key idea: Fun engagement → technical details → call to action structure
- Evidence: "Start with something fun, engaging... leads into technical details... call to action"
#### ⏱️ [11:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=675) — [H3] Demo development guidelines
- Key idea: Start with quickest prototype, iterate based on feedback
- Evidence: "Quickest thing you can prototype and prove the idea and then iterate from there"
#### ⏱️ [13:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=810) — [H1] Sticker machine technical architecture
- Key idea: Servos with wire coils controlled by Raspberry Pi through servo board
- Evidence: "Basic movement of how this vending machine works... wire coiled around a servo"
#### ⏱️ [16:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1005) — [H2] Hardware components and wiring
- Key idea: Simple wiring with no soldering required, color-coded for maintenance
- Evidence: "Four wires that go into the Raspberry Pi... no soldering required"
#### ⏱️ [18:20](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1100) — [H3] Cardboard prototyping approach
- Key idea: Start with cardboard before investing in laser cutting or 3D printing
- Evidence: "Cardboard prototyping is fantastic... allows you to iterate very quickly on the idea"
#### ⏱️ [20:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1215) — [H2] Web interface development
- Key idea: TypeScript app with Three.js animations, 10 lines for hardware control
- Evidence: "Code to actually control the hardware was about 10 lines. The rest was building the quiz"
#### ⏱️ [22:30](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1350) — [H3] Integration and customization options
- Key idea: WebRTC communication enables integration with any web service
- Evidence: "You can start to integrate... custom quiz, web hooks, launch cloud servers"
#### ⏱️ [26:45](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1605) — [H1] Demo deployment best practices
- Key idea: Bring backup Wi-Fi, power strips, spare parts, and debug controls
- Evidence: "Bring your own Wi-Fi... power strips... administration and debug controls"
#### ⏱️ [30:15](https://www.youtube.com/watch?v=LeKG27vfRCs?t=1815) — [H2] Live demonstration and debugging
- Key idea: Real-time hardware control through web interface for troubleshooting
- Evidence: "Admin dashboard to dispense stickers on demand... VNC into the Pi"
#### ⏱️ [35:00](https://www.youtube.com/watch?v=LeKG27vfRCs?t=2100) — [H3] Cost breakdown and accessibility
- Key idea: Total project cost under $200 with free software platform
- Evidence: "Raspberry Pi $40-50, display $100, servos pack of 12 for $10"
## 📚 References
- [Viam Platform](https://viam.com)
- [Jim Bennett's Confetti Cannon Blog](https://jimbobbennett.io)
- [Viam Code Labs](https://docs.viam.com/tutorials/)
- [Viam Discord Community](https://discord.gg/viam)
## 🗣️ Paraphrase
- Physical demos create more memorable experiences than slide presentations by enabling tactile learning and direct interaction with technology
- The sticker vending machine demonstrates how simple hardware (servos, Raspberry Pi) can create compelling conference demos that attract crowds and generate engagement
- Success requires careful planning including backup systems, debug tools, and graceful degradation when things go wrong during live demonstrations
## 📰 Newsletter
**Build Hardware Demos That Actually Engage Developers**
Tired of your conference booth blending into the background? Nick from Viam shows how a custom sticker vending machine became the buzziest booth demo, combining Raspberry Pi hardware with web technologies to create memorable developer experiences.
The key insight: "cheeseburger marketing" - start with something fun and tactile, reveal the technical implementation, then provide clear next steps. Physical interaction beats passive observation every time.
**Quick Start**: Begin with cardboard prototypes, bring backup Wi-Fi and spare parts, and always include admin controls for live debugging. Total cost under $200 for a crowd-drawing demo.
Resources: [Viam Platform](https://viam.com), [Hardware Tutorials](https://docs.viam.com/tutorials/), [Discord Community](https://discord.gg/viam)
## ✅ Action Items
#### DevRel
- Developer advocacy: Create tactile demos that enable hands-on learning experiences rather than passive presentations
- Education: Document full build processes including troubleshooting and deployment considerations
- Developer experience: Provide clear hardware abstraction layers that reduce complexity for software engineers
- Developer marketing: Implement "cheeseburger marketing" - fun engagement leading to technical education and clear CTAs
- Community management: Maintain active Discord/forums for real-time hardware troubleshooting support
#### Hardware
- Prototyping: Start with cardboard mockups before investing in laser cutting or 3D printing
- Components: Source reliable servo motors, Raspberry Pi systems, and breakout boards for scalable demos
- Integration: Use platforms like Viam for hardware abstraction and cloud connectivity
- Testing: Build comprehensive backup systems including spare parts, alternative power, and debug interfaces
- Documentation: Create detailed wiring diagrams, cost breakdowns, and assembly instructions
#### Conference Strategy
- Booth planning: Design interactive experiences that create crowds and social media moments
- Technical setup: Bring independent Wi-Fi, power distribution, and remote monitoring capabilities
- Engagement measurement: Track demo interactions, social shares, and post-event follow-through
- Scalability: Design demos that can be replicated by field teams without extensive hardware knowledge
- Content creation: Document build process for blog posts, videos, and community sharing
## 🧪 Hypotheses
- Physical interaction with demos creates stronger memory formation and brand recall than visual presentations alone
- Developers are more likely to try new platforms when they can immediately see cause-and-effect relationships in hardware
- Conference booth traffic increases significantly when crowds gather around interactive physical demonstrations
- Hardware demos with simple, documented architectures generate more community adoption than complex proprietary systems
### 📊 Methodology
- A/B test booth engagement between traditional slide demos and interactive hardware demonstrations
- Survey attendees on recall and likelihood to try platforms 30 days after different demo types
- Measure social media engagement and user-generated content from hardware demos vs. software demos
### ❓ Questions
- How do hardware demo costs compare to increased booth engagement and conversion rates?
- What minimum hardware complexity is required to create meaningful tactile learning experiences?
- How can hardware demos be made accessible to developers with varying physical abilities?
### 🔮 Future Research
- Investigation into optimal demo complexity vs. engagement curve for different developer audiences
- Study of hardware demo effectiveness across different cultural contexts and conference types
- Research on remote/virtual alternatives that maintain tactile learning benefits
### 💡 Implications
- Practice: DevRel teams should budget for hardware prototyping and demo transportation logistics
- Policy: Conference organizers need clearer guidelines for power, networking, and space requirements for hardware demos
- Security: Hardware demos require additional security considerations for device management and network isolation
- Education: Developer education programs should incorporate more hands-on hardware components
- Funding: Hardware demo ROI measurement requires new metrics beyond traditional software engagement tracking
### 🧠 Learning Styles Assessment
Reading level estimate: Flesch-Kincaid Grade Level 8
#### 👀 Visual learners
- Present: Hardware diagrams, wiring schematics, component photos, live demonstration
- Improve: More step-by-step visual assembly guides, component identification diagrams
#### 🔊 Aural learners
- Present: Live presentation with detailed verbal explanation of each component
- Improve: Accompanying podcast episode breaking down hardware concepts for beginners
#### 🗣️ Verbal learners
- Present: Clear definitions of technical terms, analogies to familiar concepts
- Improve: Glossary of hardware terminology, comparison tables between different approaches
#### 🧩 Kinesthetic learners
- Present: Hands-on demonstration, physical components to examine
- Improve: Take-apart kits for audiences to assemble/disassemble during presentation
#### 🧠 Logical learners
- Present: Step-by-step build process, cost breakdown, troubleshooting decision trees
- Improve: Flowcharts for component selection, performance comparison matrices
#### 🧑🤝🧑 Social learners
- Present: Q&A session, community Discord mentioned for ongoing support
- Improve: Breakout sessions for collaborative hardware building, peer code review
#### 🧘♀️ Solitary learners
- Present: Complete documentation for independent building, GitHub repositories
- Improve: Self-assessment quizzes, individual project idea generators
#### 🌿 Naturalistic learners
- Present: Discussion of recycling cardboard for prototypes
- Improve: Analysis of electronic waste considerations, sustainable hardware choices
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Clear verbal descriptions of hardware components and connections
- Improve: Detailed alt text for all diagrams, tactile description of physical components
#### Keyboard navigation
- Present: Web interface can be controlled via keyboard
- Improve: Voice control options for hands-free hardware interaction
#### Contrast and readability
- Present: High contrast display on touchscreen interface
- Improve: Adjustable text size options, dark mode for quiz interface
#### Text resizing and reflow
- Present: Responsive web interface adapts to different screen sizes
- Improve: Testing at 200% zoom, ensuring button targets remain accessible
#### Media and captions
- Present: Live demonstration with simultaneous verbal explanation
- Improve: Auto-generated captions for any recorded demo videos
#### Forms and interactions
- Present: Large touch targets for quiz interface, clear success/failure states
- Improve: Alternative input methods for users unable to use touchscreen
#### Standards reference
- Quiz interface should meet WCAG 2.2 AA standards for interactive content
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Universal appeal of personality quizzes, hardware concepts
- Improve: Localized quiz questions that work across cultural contexts
#### Inclusive language
- Present: Gender-neutral language in quiz options and technical documentation
- Improve: Avoid cultural idioms in international documentation
#### Neurodiversity support
- Present: Clear step-by-step instructions, consistent interface structure
- Improve: Options for reducing visual animations, simplified alternative interfaces
#### Representation
- Present: Focus on technical merit rather than personal demographics
- Improve: Showcase diverse community projects built with similar approaches
#### Psychological safety
- Present: Encouraging tone about learning from mistakes and iteration
- Improve: Explicit statements about beginner-friendliness, no judgment zones
### ✅ Logical Validity
#### Strong reasoning
- Deductive strength: Physical interaction enhances learning → hardware demos improve engagement
- Inductive strength: Multiple examples (confetti cannon, sticker machine) support engagement thesis
- Causal reasoning: Crowd formation creates positive feedback loop for booth traffic
- Analogical strength: Comparison to street performers gathering crowds effectively illustrates principle
#### Fallacies
- Appeal to novelty: Assumes newer/physical demos are automatically better without considering context
- Survivorship bias: Only shows successful hardware demos, not failed attempts or contexts where they don't work
#### Tone of voice
- Overall tone: Enthusiastic and encouraging while being realistic about challenges and preparation needed
### 🛡️ DARVO Analysis
- Deny: No significant denial patterns observed
- Attack: No attacks on traditional demo approaches, constructive criticism only
- Reverse victim/offender: No victim/offender dynamics
## Highlights
- Yeah. Yeah. Yeah. Hopefully at the end of this you all will feel a bit more inspired and motivated to not just build a sticker vending machine, but something else that's compelling and a physical demo. And that's a lot of what we're talking about today. Not just building what this is, but what goes into a physically compelling demo. What goes into building anything is engaging as we're trying to show off something we're teaching, something we're we're trying to demonstrate. Uh we've heard a lot about demos over the past couple days and I love it because it's allows me rolled up into this um into specifically like building something like this. Um ([View Highlight](https://read.readwise.io/read/01k9x48n7mb8dgy4pkrtfszv54))
- Tags: 👻 ai highlighted
- anything from something automatically plant watering to a sticker vending machine to, you know, uh, robotic arms, these all go around and can be something relatively simple to something super complex, but these are all robots in the way that we think about them here at BM. Um, and we can make them smarter as well with different sort of existing or pre-trained models. Uh, you don't have to have any prior experience with hardware or machine learning in order to just get started and build something that you're dreaming of. So, as Jim, ([View Highlight](https://read.readwise.io/read/01k9x48n7yzmbvjnnrh4ggqfrd))
- Tags: 👻 ai highlighted
- powerful and showing like, oh, they can go do this and they can have wildly more grand ideas than I might have because I have a shorter timeline, but they can go work on it in the background and get the support of, you know, Devril or anyone else to make it happen. And so this sticker vending machine um is made up of servos. Who's worked with a servo before? Good people. Great. Yeah, it's something that moves. It's kind of like one of your initial actuations, uh, when you're starting to get into hardware or robotics. Um, and so the ([View Highlight](https://read.readwise.io/read/01k9x48n98d56whvhaw4v7k4d3))
- Tags: 👻 ai highlighted
- And so what builds up some of these sort of uh like I said before we have here like a Raspberry Pi some servos um and like a touchcreen for embedding it all together. But there's so many other ways you can start to uh you know build out your robot your demo robot um and that could be you know you know you could use Raspberry Pi. I could have just run this all off of my laptop with a connection straight to um you know the Pi itself. Uh you can use microcontrollers if you want something a bit more portable. Webcams are really easy to integrate with if you've never done anything with ([View Highlight](https://read.readwise.io/read/01k9x48nayxakj4gyqe6dpg1yq))
- Tags: 👻 ai highlighted
- thousand words. It's very true for any sort of data. It's just how well can you use it to do something. And so if you can just start getting some basic data points from any sort of images um you can do a lot with that and you can start with just again a webcam and a Raspberry Pi or even just your laptop to get started. Another example maybe people have been hearing about some of these robotic arms that come much more approachable. Um, Hugging Face has this open source robotic arm from a a project called The Robot. It's SLO 101. And this is something you could start to control and make something even more fun. So, if you ([View Highlight](https://read.readwise.io/read/01k9x48nggwjw5qd92smgqh3nd))
- Tags: 👻 ai highlighted
- want to have something being picked up or um I know Jim had the idea of putting something like assembling Lego with robotic arms um as part of the process of learning something um you can get started with just you know again your laptop and ARM uh and you know using something that integrates with it. It doesn't have to be VM, but you know, we have stuff out of the box that does that. You can use machine learning models or whatever else you're trying to to show. And so, again, why does this overall matter? You're trying to get people to, you know, push past like the basic ([View Highlight](https://read.readwise.io/read/01k9x48nkdrs9k3aw8mq6smcjn))
- Tags: 👻 ai highlighted
- custom computer vision model and use that as part of what you're building. Um, we have a whole uh sort of build video and code lab for that. Um, and if you want to win a rover, um, we also have you can sign up for our newsletter and then folks who sign up today will be part of a um, lottery to win a rover and we'll send that to you. Um, and you can, you know, drive that around and see what happens when you bring that to your next sponsor booth. Um, that is actually everything I have today for slides. But what I want to do with ([View Highlight](https://read.readwise.io/read/01k9x48nr224ecw88b0fhjp9xy))
- Tags: 👻 ai highlighted
- just you just need to provide a Raspberry Pi or if you're really fancy, you got a Nvidia Jetson throw on there. You can now get controls over this sort of um robot. Uh, and then you can start to drive it around. You can use the IMU to give it some automation and use computer vision and drive and uh learn on it. You can add on additional sensors later if you want to get to LAR um or sort of ultrasonics and start to automate even more. Um so that's what this uh the VM rover is uh for those that are curious. >> Thank you. ([View Highlight](https://read.readwise.io/read/01k9x48ntfz79j20xcnbnhd8kw))
- Tags: 👻 ai highlighted
- an instant sort of like smart machine that we could use to make demos more engaging for uh conferences and events. So we can bring that along and we could, you know, instead of having point at a bowl, we could train a model to then maybe look for maybe certain color M&M's instead and start to then stop until or keep feeding until you find those. Um, and those are ways to nice customize uh stuff around. Uh, we just published this one to control a robot arm uh with VM. So if you want to integrate a like affordable robot arm that runs on Raspberry Pi, the Yaboom Dobbot's a good ([View Highlight](https://read.readwise.io/read/01k9x48p6ss8ea14bmzrrp92ys))
- Tags: 👻 ai highlighted