The latest articles on DEV Community by pishelin (@pishelin_6624396e0b75aeae). https://dev.to/pishelin_6624396e0b75aeae https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3637910%2F9edb4f6f-9644-4faa-8b86-9aa9ce70bde6.png https://dev.to/pishelin_6624396e0b75aeae en pishelin Tue, 08 Sep 2026 12:14:39 +0000 https://dev.to/pishelin_6624396e0b75aeae/i-built-a-backend-framework-because-express-setup-made-me-miserable-180g https://dev.to/pishelin_6624396e0b75aeae/i-built-a-backend-framework-because-express-setup-made-me-miserable-180g <h1> The Problem </h1> <p><strong>Tags:</strong> #node #typescript #webdev #programming #tutorial</p> <p>After years of Next.js, going back to Express felt like traveling back in time:</p> <ol> <li>TypeScript? Configure it yourself</li> <li>Route structure? Copy from old repos</li> <li>Middleware? Install 5 different packages</li> <li>Prisma? More setup</li> </ol> <h1> The Solution </h1> <p>Fastay - file-based routing for Node.js:</p> <p>src/<br> ├── api/<br> │ ├── hello/<br> │ │ └── route.ts # → /api/hello<br> │ ├── users/<br> │ │ └── route.ts # → /api/users<br> │ └── products/<br> │ └── route.ts # → /api/products</p> <h1> What I Learned </h1> <ul> <li>How routing actually works under the hood</li> <li>Middleware chain architecture</li> <li>TypeScript generics at a deeper level</li> <li>Documentation is 50% of the work</li> </ul> <h1> What's Next </h1> <ul> <li>[ ] Plugin system</li> </ul> <h1> Try It </h1> <p>npm install fastay</p> backend node typescript webdev pishelin Tue, 08 Sep 2026 12:12:09 +0000 https://dev.to/pishelin_6624396e0b75aeae/i-built-a-backend-framework-because-express-setup-made-me-miserable-the-problem-after-years-24o https://dev.to/pishelin_6624396e0b75aeae/i-built-a-backend-framework-because-express-setup-made-me-miserable-the-problem-after-years-24o pishelin Sun, 30 Nov 2025 20:38:45 +0000 https://dev.to/pishelin_6624396e0b75aeae/nodejs-didnt-need-another-fast-framework-it-needed-a-simple-one-e28 https://dev.to/pishelin_6624396e0b75aeae/nodejs-didnt-need-another-fast-framework-it-needed-a-simple-one-e28 <p>Most developers just want to build clear, predictable, organized APIs — without reading 300 pages of docs, memorizing magic decorators, or loading half an ORM just to return a JSON.</p> <p>But today…</p> <p>Express stopped in time.</p> <p>Nest turned into a city with too many rules.</p> <p>Fastify is excellent, but it cares more about benchmarks than real people.</p> <p>So Fastay.js was born in the middle of this chaos, with one goal:</p> <blockquote> <p>Productivity over performance.<br> Convention over configuration.<br> File-based routing without becoming a monolithic framework.</p> </blockquote> <p>No reinventing HTTP.<br> No XML disguised as decorators.<br> No enforced “enterprise architecture.”</p> <p>Just:</p> <p>modern Node.js</p> <p>a clear project structure</p> <p>good DX</p> <p>and straightforward APIs</p> <p>Enough to stay out of your way.</p> <p>We’re not trying to be the fastest.<br> We’re trying to be something you can understand in 10 minutes<br> and maintain for years.</p> <p>If Fastify is a V8 engine,<br> Fastay.js is the lightweight motorcycle:<br> simple, functional, and ready to work.</p> <p>Sometimes, that’s all you really need.</p> <h1> javascript </h1> <h1> node </h1> <h1> webdev </h1> <h1> backend </h1> <h1> opensource </h1> <h1> programming </h1> <h1> api </h1> <h1> framework </h1> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmaee4ntn9mdwioagj1v5.jpg" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmaee4ntn9mdwioagj1v5.jpg" alt=" " width="800" height="520"></a></p>