From zero coding background to hardware hacker: How Cursor + a Raspberry Pi makes AI fun

The speaker discusses a series of creative hardware and software projects that blend digital communication with physical outputs. One central project is a web-based messaging system where users can send messages through a website that are then printed on a mini thermal printer via a Raspberry Pi. This system uses a Convex database to log messages and allows for tangible, real-world interaction with digital content. The speaker also explores the use of retro hardware, such as thermal receipt printers and dot matrix printers, integrating them with modern tools like AI and APIs to create engaging, tactile experiences.

Another key project involves building a pager system for children using the Spoke radio network, aiming to recreate an analog, 90s-style communication experience. The pagers, sourced through medical resellers, receive messages via a complex but functional email relay system involving Cloudflare Workers and custom email routing. The speaker also introduces the concept of a "personal API" - a playful yet practical idea where individuals can share personal preferences (like coffee orders or favorite restaurants) via an API to streamline thoughtful interactions. These projects emphasize physical-digital integration, creative problem-solving, and using technology to strengthen human connections, often by repurposing outdated systems in innovative ways.

• What if you built a personal API to automate thoughtful gestures for clients or users?

  • Move: Define a simple JSON endpoint (hosted on a serverless function) that returns your public preferences: favorite coffee order, preferred meeting times, contact methods, etc. Use this as a template to let early customers or collaborators "integrate" with you.
  • Why Now?: AI agents and automation tools are starting to act on behalf of users - having a machine-readable way to share your preferences lowers friction in scheduling, gifting, or collaboration, especially in AI-native workflows.
  • Expected Upside: Early adopters in the AI/developer community may reference or build around your API (e.g., auto-scheduling meetings at your preferred time), increasing visibility and positioning you as a practical innovator in personal automation.

• What if you turned a thermal printer into a physical notification hub for your SaaS?

  • Move: Connect a $20 thermal printer to a Raspberry Pi, then route key SaaS events (new signup, payment received, feature request) to print real-time receipts with details.
  • Why Now?: Physical feedback loops increase founder awareness and emotional connection to user activity - especially valuable when bootstrapping alone and lacking team-based energy.
  • Expected Upside: Tangible, audible notifications create dopamine-driven feedback (e.g., hearing the printer buzz on a new sale), reinforcing motivation and helping you spot patterns (e.g., when users drop off) faster than silent dashboards.

• What if you launched a retro messaging API using a pager or dot matrix printer as the backend?

  • Move: Set up a public API (e.g., /send-pager) that forwards messages via email to a real pager or prints them on a dot matrix printer, then responds with a confirmation including a timestamped photo of the output.
  • Why Now?: Nostalgic hardware is gaining attention in dev communities (e.g., TerminalTwo, Cardputer); launching a "slow, analog" API contrasts with real-time norms and attracts attention on social coding platforms.
  • Expected Upside: Developers tweet about sending messages to a literal pager, generating organic virality and inbound leads for your other tools or services - while proving you ship quirky, working hardware integrations.

• Set up a web-accessible hardware project using a Raspberry Pi and a thermal printer to create tangible outputs from digital inputs, starting with a simple message form and server-side print trigger.
• Use AI tools like Cursor to systematically brainstorm and validate hardware requirements before purchasing components, ensuring compatibility and reducing waste from incorrect purchases.
• Implement a fallback logging system (e.g., in a Convex database) to record all incoming messages or actions - even failed print attempts - for reliability and data continuity in hardware-connected apps.
• Build a personal API endpoint to share curated preferences (e.g., coffee order, favorite restaurant, travel dates) that others can programmatically access to reduce friction in personal coordination or gift-giving.
• Create a message-forwarding automation pipeline using Cloudflare Workers and email services (e.g., Resend and Gmail) to bridge modern APIs with legacy systems like paging networks or restricted email endpoints.