Made an ESLint plugin for catching duplicate API routes I've run into this issue more times than I'd like to admit, spending hours debugging why routes aren't working, only to discover I have: - GET /users/:id (file A) - GET /users/:userId (file B) They're the same route, just with different param names. Which one actually runs? Depends on which file loads first. Standard ESLint doesn't catch this, so I built a plugin that does. It scans your entire codebase, understands router prefixes (app.use('/api', router)), and normalizes param names so: id and: userId are flagged as conflicts. Works with Express, Fastify, and NestJS. Just published it would love feedback from anyone working on larger APIs where this slips through code review. npm install --save-dev eslint-plugin-route-guard npmjs.com/package/eslint-plu… Hope this saves someone else the debugging headache.

new account: @_uzair_dev that's where im gonna be posting and engaging now, see yall there 🚀

Hey devs, which will you build first? - Frontend - Backend

Be honest, developers: When you see a new framework, do you: - Immediately try to build something with it - Scroll past and stick to what you know - Overthink and never use it

How many hours do you actually code per day? - 1–3 hours - 4–6 hours - 7–9 hours - 10 hours

just hit 2,700 followers we're growing 🔥

What do you think kills more startups? - Running out of motivation - Running out of money

anyone know how to fix this?

What's the hardest part of coding? - Debugging - Understanding requirements - Writing clean code - Dealing with legacy code

What actually slows you down more? -Writing code -Debugging -Deployment -Decision making

What’s one thing you wish someone explained better when you started coding?

Which would you choose for your career growth early on? -Startup (fast learning, more responsibility) -MNC (stability, structured growth, brand value)

Be honest… do you actually understand your code or just make it work?

Which is harder to learn: frontend or backend? And why?