Urgent.News

What's breaking now, across thousands of outlets.

Monday, 31 August 2026 Reading Room

Tech

Badger: An E-Ink Badge I Use For Conferences

I attend conferences regularly, and for years I’ve wanted a badge that makes it easy for people to find me online. In 2019, I attended defcon and built defpi , a goofy raspberry pi powered badge. While that was fun I wanted a bit more turnkey and I found just what I wanted with a Badgeware Badger (nerdy domain hack badgewa.re). Since my use case is to just have my socials via QR I chose the e-ink…

dev.to ·

I am Sean Boult, a developer, hacker, and creator who attends conferences regularly. For years, I have been seeking a badge that allows for easy online identification. In 2019, I attended defcon and created defpi, a playful Raspberry Pi-powered badge. However, I desired a more user-friendly solution, which led me to the Badgeware Badger.

The Badger, a domain hack badgewa.re, comes equipped with an RP2350 WiFi module, a 1000mAh battery, a USB-C interface, and is powered by MicroPython. Given my preference for QR codes, I opted for the e-ink version. I utilized Codex to generate the necessary Python code, which created QR profiles linking to my LinkedIn and personal website.

The Badger's default screen is straightforward, directing users to either my LinkedIn or personal site. A simulator allows me to test the code before deploying it to the badge. Using the command 'make sim' builds the simulator, enabling local testing with the command 'make deploy' on the connected badge. The simulator's controls include flipping between badge and social screens, changing background patterns, and hot reloading the app. To deploy, simply connect the Badger via USB-C, double-tap RESET, and run 'make deploy'.

This process validates the app, copies the required Python and image files, and reboots the badge. For those attending Commit Your Code 2026 in Dallas, I encourage you to find me to showcase the Badger. Follow me for all things tech.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How I tested Row Level Security before shipping a SaaS starter kit (so one user can't see another's data)

When you're building a multi-tenant app, there's one bug category that's worse than any other: a user seeing someone else's data. Not a crash, not a broken button — a genuine privacy failure.

  • Tested Row Level Security with Supabase to prevent users from viewing other users' data.
  • Created a policy pattern for owner-scoped tables to filter rows based on authenticated user's ID.
  • Conducted impersonation tests to verify RLS policy effectiveness in both read and write operations.

·dev.to

CI/CD Mistakes That Are Quietly Costing Your Team Deploy Time

Most teams don't notice their CI/CD pipeline is broken — they just notice that deploys "feel slow" and shrug it off as normal. It isn't.

  • Running full test suite for every change wastes time on unrelated modifications
  • Lack of caching between builds re-installs dependencies on each pipeline run
  • Sequential steps that don't depend on each other are executed one after another

·dev.to

The wait queue is just a channel: building a small distributed lock server in Go

Sooner or later you hit the same small problem: two services, on two machines, want to touch the same thing at the same moment — append to a shared file, update a row nobody is fencing, call an API…

  • Locking-Center is a compact Go lock server for distributed systems
  • Uses Go channels to implement lock-free locking mechanism
  • Includes request context map for cancellation and timeout handling

·dev.to

More from Monday 31 August →