Just wrapped up the core setup for my e-commerce API (Impextech): Auth, Products, and Users. Everything is running on Node.js, Express, and TypeScript. Instead of just getting it to work, I spent this week focusing on security, keeping the code clean, and fixing some annoyances in my dev environment. Here’s a breakdown of what I built and a few "gotchas" I learned along the way. I split everythin
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
Multi-tenancy is the economic engine of SaaS. Sharing infrastructure across customers reduces cost and simplifies operations. But it introduces a risk that can end your business overnight: tenant data leakage. When one customer can see another customer's data — even accidentally — the consequences are severe. Regulatory fines, contract termination, public disclosure requirements, and irreparable t
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
The first AI feature I shipped on a flat plan lost money on the third user who discovered it. Not slowly. Immediately. He was running a script through it on a loop because the UI did not stop him from doing that, and his single account burned through more in API costs that week than the feature was supposed to make in a month. I shipped the fix on a Sunday and rewrote the pricing on a Tuesday, and
From Prompt to Production: AYW Workflow Case Study How we built a production-ready customer support chatbot in 6 hours (with full understanding, security review, and audit trails). Build a customer support bot that can: Handle 500+ concurrent users Integrate with Zendesk ticketing Support English + Spanish Maintain audit logs for SOC2 compliance Deploy on AWS with auto-scaling Traditional estim
Hey everyone, I shared this earlier as a CLI to analyse npm packages before installing. Since then, I’ve added something I think is even more useful: 👉 You can now scan GitHub repos before cloning or running them npx guard-install --repo https://github.com/user/repo There’s a growing pattern (especially in crypto interviews / side projects): “Clone this repo and run it locally” Some of these rep
Tired of writing the same Socket.io setup every project? 😩 I built quick-socket — install it and get real-time chat working in minutes. npm install quick-socket ## What you get out of the box 📦 ✅ Chat rooms ## Time saved ⏱️ Socket setup → 3 hours becomes 1 minute Room management → 4 hours becomes 1 line Typing indicator → 1 hour becomes 1 line Read receipts → 3 hours becomes 1 line Total sa