Hi, I am Abhishek Rajput
🌐 Bharat 🇮🇳
💼 Frontend Developer
⭐️A Ardent Developer
💻 Windows
❤️ JavaScript, React js, Next js, Node js.
#FrontendDeveloper
Do follow me if you’re interested in any of these:
Javascript #Reactjs
Web Dev❤️ #Nodejs
Nextjs.
@careinsuranceIN@CareHealthIndia Your app has not been working since yesterday and keeps showing “We are not able to process your request. Please try again later.”
How can customers access policies and services if the app is unavailable? Please fix this issue.
Booked my first UPSRTC ticket from Bijnor to Meerut, but no bus was available at the boarding point and there was no support or guidance for passengers. Very disappointing experience. Requesting @UPSRTCHQ to resolve this issue.
#UPSRTC#UPTransport@dayashankar4bjp
Summary of Monorepo tRPC
It was quite overwhelming session by @piyushgarg_dev sir. Will revise and rewatch the recording few times to understand this structure better.
@ChaiCodeHQ
When Apple MacBooks already have a built in Speech to Text, Why should someone use WisprType?
Can your Speech to Text do this?
WisprType's Smart Typing understands you application level context and based on that it understands your "Intension" rather than "Words".
Because, When you want to speak at the speed of your thoughts, "Intension" matters rather than "Words". So Intension >>> Words 🔥
WisprType is a Free alternative to @WisprFlow & @superwhisper built for Apple Silicon ❤️
A lot of backend developers underestimate folder structure early on.
Not because they don’t care, but because everything works… until it doesn’t.
When your app has 5 files, anything works.
When it has 500 files, structure decides:
→ how fast you debug
→ how safely you add features
→ whether new engineers understand your code
This is not a style preference.
This is what keeps your system from collapsing under its own weight.
---
Most beginners think
folder structure = grouping files.
That is only half the story.
The real idea is:
each layer should have one clear responsibility
For a Node.js app, it often looks like:
routes → handle HTTP
controllers → translate request/response
services → business logic
repositories → database access
models → data shape
Simple rule:
If you mix these, you create confusion. If you separate them, you create clarity.
----
Adding a feature is not just writing code.
It is answering:
→ where should this logic live?
→ what should it depend on?
→ what should it NOT depend on?
If your structure is weak:
→ logic leaks everywhere
→ files become huge
→ changes break unrelated things
If your structure is strong:
→ you know exactly where to write code
→ changes stay local
→ debugging becomes faster
----
Bad approach:
→ route calls DB directly
→ business logic scattered
Good approach:
route → middleware → controller → service → repository
Now when something breaks:
→ you don’t search the entire codebase
→ you follow a clear path
Note: Sometimes "repository" code written in "service" as well. That's also fine. It's completely your preference.
----
Ask this for every file:
→ what is its responsibility?
→ who is allowed to call it?
→ what should it never know about?
If you can answer these clearly, your structure is probably good.
----
#NodeJS#NextJS#BackendDeveloper
✅ React Basics Day 1
Topics Covered:
1. Component architecture
2. Reusable components
3. Props
4. Children
5. State (useState)
6. useEffect
7. API handling
8. List rendering
9. Conditional rendering
Thank you @jaaaani404 for your handwritten notes.
PS: Used her notes to generate this notes
Introducing GPT-5.5
A new class of intelligence for real work and powering agents, built to understand complex goals, use tools, check its work, and carry more tasks through to completion. It marks a new way of getting computer work done.
Now available in ChatGPT and Codex.
🚀 Backend Engineering Series — Day 9: Designing REST endpoints
Bad endpoints are confusing. Good ones feel obvious-like anyone could guess them without reading the docs.
Here's the complete guide to designing endpoints & handling HTTP methods correctly.
🚀 Backend Engineering Series — Day 8: REST API — the paradigm that powers most of the web.
Roy Fielding defined it with 6 architectural constraints in his 2000 dissertation. Most tutorials only mention 3. Here's the full picture.