Abhishek Rajput

🧑‍💻Full Stack Developer | ☁️AWS Enthusiast | Skilled in React.js, Next.js, Node.js & Express.js | Open to exciting opportunities | Let’s build together 🚀

[Abhishek Rajput @BroCode1508]

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.

[Abhishek Rajput @BroCode1508]

@narendramodi @POTUS @realDonaldTrump Nifty 50 23000

[Abhishek Rajput @BroCode1508]

@nirudhuuu @piyushgarg_dev 😂😂

[Candy樂兒 @candyyueliu]

Introducing Monako Glass 👓

The world's first wearable Linux computer in glasses form.
Run Claude Code, Codex, and any coding agent — anywhere.

[Abhishek Rajput @BroCode1508]

@rutu609 🤨

[Piyush Garg @piyushgarg_dev]

C10K Problem 🫪

[Ankit @UnrealAnkit]

Bangalore Jobs Seekers Kit - https://t.co/dQPcD3q96T

Gurgaon Job Seekers Kit - https://t.co/RAqJkhtoKp

Hyderabad Job Seekers Kit - https://t.co/s1JvBIpK0h

Mumbai Job Seekers Kit - https://t.co/hU8rJt9H60

Would help someone!!

[Abhishek Rajput @BroCode1508]

@nirudhuuu @mannupaaji 😂

[Abhishek Rajput @BroCode1508]

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

[Tushar Rajpoot @tush_tr604]

If you’re building a new application, you probably do NOT need AWS services in the initial phase. 🧵

[Sagar Shiroya @sagarshiroya_x]

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

[Sagar Shiroya @sagarshiroya_x]

May 17 - MonoRepo Setup with tRPC Session Notes✅

[Tushar Rajpoot @tush_tr604]

Just released new version
https://t.co/ITZQa36FVb

[Randhir Jaiswal @MEAIndia]

List of outcomes (7 in total) : Official visit of PM @narendramodi to UAE ⬇️

[Piyush Garg @piyushgarg_dev]

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 ❤️

[Abhishek Rajput @BroCode1508]

@sagarshiroya_x @jaaaani404 @ChaiCodeHQ Great notes 🫵🏻

[Sagar Shiroya @sagarshiroya_x]

Express.js Cheatsheet

@ChaiCodeHQ

#ChaiCode #ExpressJS #NodeJS

[Sagar Shiroya @sagarshiroya_x]

Step by step guide of how JWT sign() works behind the scene

#jwt #jsonwebtoken

[Sagar Shiroya @sagarshiroya_x]

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

[Abhishek Rajput @BroCode1508]

@sagarshiroya_x Change root for every deployment

[Sagar Shiroya @sagarshiroya_x]

✅ React Basics Day 2 Notes

- Conditional Rendering
- Manual and React Hook Forms
- Tanstack Routing
- Auth services on front-end using axios

@ChaiCodeHQ