A LinkedIn recruiter pitched me a remote "Software Engineer at a DEX" project this week. Reasonable comp range, tech stack squarely in my wheelhouse. After a couple of friendly exchanges, she asked me to "review the codebase before the technical interview" and sent me a GitHub repo link plus a Calendly invite for the call. The repo was malware. It didn't get me, but it's something developers shoul
TL;DR: I built ChessDada — a free multiplayer chess platform inspired by old Yahoo Chess. No signup, no download, just instant browser-based chess. Built with Node.js, Socket.IO, and chess.js. Modern chess sites are bloated. Chess.com forces you through signup. Lichess defaults to account creation. The "5-second click and play" experience that made Yahoo Chess legendary in the 2000s is essentially
How intentional loading decisions keep your app fast at scale. Frontend performance is not a late-stage cleanup task. It’s not tech debt. It’s a set of decisions we make every day while we code — what we load, when we load it, and how we render it. The answer depends on the importance of the code, its size, and when the user actually needs it. Get that wrong, and the browser pays for everything
The EU's Digital Product Passport (DPP) requirement is moving from regulatory text to technical reality. Under the Ecodesign for Sustainable Products Regulation (ESPR), products sold in the EU must carry a DPP—a machine-readable identifier linking to standardized lifecycle data. For developers and compliance teams, 2026 marks the year where pilot programs transition to real deployments. Here's wha
TL;DR: I built a P2P file transfer tool that runs entirely in the browser. No install, no server relay, no account. Here's what I learned about WebRTC data channels, resumable transfers, and the browser storage mess along the way. Most file transfer tools follow the same pattern: upload to a server, get a link, the recipient downloads from that server. Your file sits on someone else's infrastructu
I’m going on a short vacation this week, so this post is coming out a bit earlier than usual. I actually had a different, more “useful” topic in mind — something educational, something responsible. But then I came across this fascinating article: I don’t like Tailwind. Sorry not sorry written by @freshcaffeine , and I couldn’t get it out of my head. So I decided to write a response instead. I actu
Live: https://nulkratos-core.web.app GitHub: https://github.com/nulkratos/nulkratos-core Every "private" messenger I found had the same tradeoffs: Signal → needs your phone number. That's an identity anchor. Telegram → not E2E by default. Server-side messages. WhatsApp → Meta. Enough said. Matrix/Element → self-host complexity, still needs an account. Briar → great, but mobile-only and requires i
The problem we kept seeing Product, marketing, and CX teams want on-site feedback, NPS, and lightweight announcements (changelog nudges, maintenance banners, promos) on real pages—marketing sites, docs, and product surfaces. another heavy client SDK or a multi-week integration just to ship those surfaces. a small script + a widget on the page. Saytics—what we optimized for, the tradeoffs that fa