Developer Builds Custom E-Ink Conference Badge with QR Code Social Links

·1 views

A developer has created a personalized e-ink conference badge using the Badgeware Badger 2350, a device powered by an RP2350 chip with WiFi, a 1000mAh battery, and MicroPython support. The badge displays QR codes linking visitors to the creator's LinkedIn and personal website, making it easy to connect at events. Several hundred lines of Python code were written with AI assistance to power the badge's functionality. The Badgeware platform includes a desktop simulator, allowing developers to test their code locally before deploying it to the physical device via USB-C. The creator plans to showcase the badge at the Commit Your Code 2026 conference in Dallas.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Archify Open-Source Tool Brings Validation and Structure to AI-Generated Architecture Diagrams

Archify is an open-source diagramming and validation engine built by developer tt-a1i to address reliability issues in architecture diagrams produced by AI coding agents like Claude Code, Cursor, and Codex CLI. Instead of generating unstructured markdown charts, it requires AI agents to output a typed JSON Intermediate Representation that is then compiled deterministically into interactive HTML and SVG files. The tool validates layout hierarchies, node boundaries, and structural relationships before rendering any visual artifact. Archify supports five diagram types — including architecture, workflow, sequence, data flow, and lifecycle — and enables side-by-side snapshot diffing during pull request reviews. It integrates with modern AI coding environments via a simple CLI command and exports diagrams in formats including SVG, PNG, and WebM animations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds minimal distributed lock server in Go using buffered channels

A developer has released Locking-Center, a lightweight distributed lock server written in Go, designed to serialize access to shared resources across multiple services and machines. The tool uses a single buffered Go channel per key to represent lock state, where sending acquires the lock and receiving releases it. Crash safety is ensured through a write-ahead log with CRC32C checksums, and log compaction is handled via atomic file renames to prevent data loss during failures. The wire protocol is intentionally minimal — a single TCP connection per request with a one-byte response — making it straightforward to implement clients across nine languages including Go, Rust, Python, Java, and C. The project aims to offer a simpler alternative to Redis-based locking or full consensus systems for teams needing a standalone, dependency-light locking primitive.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer shares SQL impersonation method to verify Supabase Row Level Security in SaaS apps

A developer building a multi-tenant SaaS starter kit using Next.js, Supabase, and Stripe wanted to verify that Row Level Security (RLS) policies actually prevented one user from accessing another's data. Rather than assuming the Postgres-based policies were correct, they ran impersonation tests directly in the SQL editor by temporarily assuming a user's identity within a rolled-back transaction. The test confirmed that RLS silently filters out unauthorised rows — returning zero results instead of an error — which is the expected success signal. The same approach was applied to write operations, ensuring that delete attempts on another user's rows returned zero rows affected. The developer notes the test takes about two minutes and is particularly valuable for catching privacy failures before they reach production.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Six CI/CD Pipeline Mistakes That Silently Slow Down Your Team's Deploys

Many engineering teams accept slow deployment pipelines as normal, but common misconfigurations are often the real cause of wasted time. Key issues include running full test suites for trivial changes, skipping dependency caching, and executing independent jobs sequentially instead of in parallel. Mismatched staging and production environments also force teams to add manual verification steps, compounding delays over time. Slow or complex rollback processes make teams hesitant to deploy frequently, which ironically increases risk by bundling more changes into each release. Experts recommend targeted fixes such as path-based triggers, infrastructure-as-code, and treating rollback as a standard pipeline action rather than an emergency procedure.

0 comments Read more at DEV Community