Arpit 力

Supposed to study chemistry. Building projects instead 👨‍💻 | Web dev + AI/ML | Gwoc'26 winner 🏆 | Want to go 🇯🇵 | Watch this space ↓

[Arpit 力 @arpit_codes]

I'm enrolled in a chemistry degree.
But that's not my story.
Here's what I'm actually building - and where I'm going 👇

[Arpit 力 @arpit_codes]

Genuine question for backend devs
Why does CORS feel like it's personally attacking you every single time? 😭
Frontend and backend on different origins and suddenly the browser acts like they're enemies
What's the cleanest way you've handled this in production?Drop your approach

[Arpit 力 @arpit_codes]

@Siddhant28_08 Let's connect

[Arpit 力 @arpit_codes]

Sometime I think about how much time I wasted in my first year of college because of my mental state, I just regret everything I've done. I wish I could go back in time.

[Arpit 力 @arpit_codes]

@salujamehak5 Even if they didn't crossed 75%, if they make in the top 20% student of the respective board then they are eligible for jee (20 percentile rule), respective boards will release the marks required to be in top 20% students. So if somebody really did their hardwork, they'll be paid

[Arpit 力 @arpit_codes]

During SIH, no one let me join their team.Not because I couldn't code.Because I was from chemistry.Watched people worse than me walk into SIH with full teams.I sat alone.
Few months later, Google Winter of Code.2nd among 300 students.Mostly CSE and AI.
Nobody excludes you twice😇

[Neeraj @neerajjj6785]

Programming languages and where they actually shine:

GO
• Cloud-native / DevOps tooling
• Backend services & microservices
• High-concurrency applications
• Networking systems

RUST
• Embedded systems / OS
• High-performance tools & APIs
• Systems-level programming
• Blockchain & WebAssembly

NODE.JS
• REST / GraphQL services
• Serverless workflows
• Backend APIs
• Real-time apps (chat, streaming)

TYPESCRIPT
• Full-stack apps
• Large-scale web systems
• Frontend (React / Next.js)
• Backend (Node.js)

PYTHON
• AI & machine learning
• Automation & scripting
• Data science & analytics
• Backend APIs & services

JAVA
• Enterprise backend systems
• Banking & fintech apps
• Android development
• High-scale distributed systems

Which one are you betting on
for the next 3 years?

[Arpit 力 @arpit_codes]

@moonchild23580 japan's countryside areas

[Arpit 力 @arpit_codes]

@SahilExec Two flaws:
1. Returning "200" for a blocked request is wrong should be "429 Too Many Requests".
2. Requestcount alone is meaningless without scope. Rate limiting should be per user/IP/API key over time.
Although I don't know the fix 🥲

[Arpit 力 @arpit_codes]

What's one resource that actually taught you web dev better than anything else?
Drop it below 👇
Building my list 📚
#webdev #webdevelopement #coding

[Arpit 力 @arpit_codes]

I hope this learning will give a better direction in my career.

[Akshay Saini @akshaymarch7]

I think AI is quietly creating a dangerous generation of software engineers.
And nobody is talking enough about it.

A lot of developers today can build things faster than ever before.

But fewer developers actually understand what they are building.
That’s the scary part.

I recently noticed something while talking to students and engineers.

People can now generate:
0. React components
1. APIs
2. backend architecture
3. SQL queries
4. Docker configs
…within seconds.

But the moment something breaks unexpectedly, many get completely stuck.

Because debugging requires understanding.
And understanding takes struggle.

Earlier, when we used to build things manually, we would suffer through:
0. weird errors
1. broken deployments
2. dependency hell
3. state management bugs
4. performance bottlenecks

At that time it felt painful.
But that pain was actually building engineering intuition.

AI removes a lot of friction.
Which is amazing.
But it can also remove the learning.

And I think this is where the gap between “developers” and “engineers” will become very visible over the next few years.

The developers who survive AI won’t be the ones who can generate code fastest.

It will be the ones who can:
0. think deeply
1. debug systems
2. make engineering decisions
3. understand tradeoffs
4. simplify complexity

Code generation is becoming cheap.
Judgement is becoming expensive.

That’s probably the biggest shift happening in software engineering right now.

[Arpit 力 @arpit_codes]

Bought 100xschool combined bootcamp. I already know basics of web D, mainly bought it for Ai and devops. Syd isse hi kuch "भला" ho jaye
@kirat_tw @100xDevs @100xSchool

[Arpit 力 @arpit_codes]

@Riya_K11 Any learning you want to share with those who are getting into second year?

[Arpit 力 @arpit_codes]

Still learning all of this myself while building real projects
Documenting everything publicly the wins, the bugs, the breakthroughs.
Follow along if you're on the same journey
What async mistake caught you off guard? Drop it below

[Arpit 力 @arpit_codes]

JavaScript's async model confused me for weeks.
Then it all clicked.
Here's the evolution from callback hell to clean async/await and the mistakes nobody warns you about

[Arpit 力 @arpit_codes]

So the async JS journey looks like this:
→ Callbacks works, but messy
→ Promises cleaner, chainable
→ Async/Await readable, modern
Common mistakes to avoid:
→ Forgetting .catch()
→ Sequential awaits for parallel tasks
→ Skipping try/catch
Save this thread for later