neelIsBroken

Most GraphQL repositories teach you how to write resolvers. Very few teach you what happens when your application gets real users. So I built a production-grade GraphQL backend that goes beyond CRUD and explores the engineering problems most tutorials never touch. Some of the challenges it solves: → How do you prevent the N+1 query problem? → How do GraphQL subscriptions work across multiple servers? → How do you invalidate JWTs without maintaining a blacklist? → Where should business logic actually live? → How do you structure a GraphQL codebase that doesn't become a mess after 6 months? To answer those questions, I implemented: • DataLoader for query batching • Redis-backed Pub/Sub for scalable subscriptions • JWT Auth + Role-Based Authorization • Service & Repository Pattern • Request-scoped Context Injection • Rate Limiting • Graceful Shutdown • Prisma ORM The biggest lesson? GraphQL isn't the hard part. Designing systems around GraphQL is. If you've only seen tutorial-level GraphQL projects, this repo will show you what comes next. Repo ↓ github.com/Neel-stack-deb… #graphql #backend #nodejs #softwareengineering

This USA team is fascinating. Clearly shows the growth of footballing culture in the states

Good morning guys. Today's agenda implementing the ReAct paper, Plan and execute paper and the Reflection Paper with an easy-to-understand fashion just like my GraphQL repository, so that any beginner can level up their Agentic AI knowledge by studying my repo. Shoot any questions

@abhijeet_tw niceee

finally completed it guys now going to sleep good night you all

@sidtwtts hi Sid:) followed

@why_always_Neel Let’s connect

Currently at 55 followers Looking to connect with people interested in • Startups • AI • Engineering • hackathon • Systems • football If you’re building, learning, shipping, or just figuring things out let’s connect :)

@josh95235 nice man:) followed

@why_always_Neel I'm into AI

@automatex_labs yes mate:) followed

@why_always_Neel let’s connect

I’m looking to #CONNECT with more developers who are building, learning in public, and talking tech. If that’s you, let’s connect.

@jingconan that's amazing would like to contribute someday:) followed

@why_always_Neel Hi! Let's Connect! I am building DeepVista.ai, which helps founders to turn ideas to reusable workflows

@sflorimm insane bio you're living my dream Floro. followed:)

@why_always_Neel let's connect

@mikeydsoftware followed you Mike :)

@why_always_Neel That's me, let's connect

@ThieryRakt followed you Thierry :)

@why_always_Neel Hi, let's connect

@RobGuerra90 Mostly AI infra, as that's where I am working on currently, but I am all in for low-level systems and scalable infrastructure, lots of experts here on X. Every day, new learning

@why_always_Neel Sounds like a great way to level up, what kind of projects are you hoping to collaborate on or learn from others about

@ascending_ai nice to meet someone of the same sub domain:) followed.

@why_always_Neel I build AI Automation systems, let's connect

@joseph_mugen followed you Mugen :)

@why_always_Neel Let's connect Neel

@LukitunXYZ definitely! followed:)

@why_always_Neel lets connect

@treasdesk @treasurydesk that's wonderful rooting for you man

@why_always_Neel Hi! Let’s connect. I’m building @treasurydesk — helping finance teams make stablecoin and on-chain treasury activity easier to review.

@CyborgThinkAI well I like to keep it short,

Hard to find connection when all there is on your profile card is "Backend | Books". It's like saying "Tradesman | TV"

@0xlelouch_ Backend for the frontend approach

You need to support both mobile app (needs minimal data) and web dashboard (needs full details) from same API. How will you design the API efficiently? Topic: API Versioning & Design

@HxrshitYadav @kirat_tw but the thing is 90% of kirat projects are extended CRUDs

Harkirat just dropped a video that genuinely made me uncomfortable. And I think every CS student and fresher in India needs to hear this. Here is what is actually happening in the software industry right now. > Meta laid off 10% of their engineers recently. But that is not even the scary part. Another 20% of their remaining engineers, around 4000 to 5000 people, are no longer writing code. > They are doing data labelling now. One in every five software engineers at Meta. > Labelling data. > To train the AI that will eventually replace them. Let that sink in for a second. And it is not just Meta. > Companies now have internal leaderboards that track how many AI tokens their developers use. Your performance review can be affected by how much you use AI tools. They literally call it "token maxing." The CRUD developer era is over. > You know the one. Learn DSA > Build a basic project > Get placed at a service company That pipeline worked in 2021. > It is dying in 2026. So what actually survives? Three types of engineers will thrive going forward. > THE BUILDER - Deep computer science fundamentals - System design. Applied AI - OS, concurrency, databases, deployment Not someone who knows syntax. Someone who understands how systems actually work. > THE SYSTEMS MANAGER - Not managing human teams anymore. - Managing networks of AI agents instead. Former engineering managers with real experience will own this space. > THE FRONT LINER - Helping companies integrate AI models into their existing systems. - Strong communication - Strong debugging skills - Less coding, more problem solving Pays extremely well. The opportunity is not gone. It has just shifted. > Startups are still hiring aggressively. Salaries from 8 LPA to 50 LPA for the right people.Harkirat Singh just dropped a video that genuinely made me uncomfortable. And I think every CS student and fresher in India needs to hear this. Here is what is actually happening in the software industry right now. > Meta laid off 10% of their engineers recently. But that is not even the scary part. Another 20% of their remaining engineers, around 4000 to 5000 people, are no longer writing code. > They are doing data labelling now. One in every five software engineers at Meta. > Labelling data. > To train the AI that will eventually replace them. Let that sink in for a second. And it is not just Meta. > Companies now have internal leaderboards that track how many AI tokens their developers use. Your performance review can be affected by how much you use AI tools. They literally call it "token maxing." The CRUD developer era is over. > You know the one. Learn DSA > Build a basic project > Get placed at a service company That pipeline worked in 2021. > It is dying in 2026. So what actually survives? Three types of engineers will thrive going forward. > THE BUILDER - Deep computer science fundamentals - System design. Applied AI - OS, concurrency, databases, deployment Not someone who knows syntax. Someone who understands how systems actually work. > THE SYSTEMS MANAGER - Not managing human teams anymore. - Managing networks of AI agents instead. Former engineering managers with real experience will own this space. > THE FRONT LINER - Helping companies integrate AI models into their existing systems. - Strong communication - Strong debugging skills - Less coding, more problem solving Pays extremely well. The opportunity is not gone. It has just shifted. > Startups are still hiring aggressively. Salaries from 8 LPA to 50 LPA for the right people. Remote roles paying $5000 a month exist right now. > But only for engineers who actually understand what they are building. Not for people who just prompt ChatGPT and copy paste the output. Six months of serious skill building right now could completely change where you land. The question is what are you actually doing with those six months. > But only for engineers who actually understand what they are building. Not for people who just prompt ChatGPT and copy paste the output. Six months of serious skill building right now could completely change where you land. The question is what are you actually doing with those six months.