Ritesh Roushan

7.4K posts

Ritesh Roushan banner
Ritesh Roushan

Ritesh Roushan

@devXritesh

Building prod-grade backend systems at scale 🇮🇳 • System Design • Microservices • AI Infra • Real prod lessons | Founder: The 1% Engineers

172.16.0.1 Bergabung Şubat 2018
769 Mengikuti1.2K Pengikut
Ritesh Roushan
Ritesh Roushan@devXritesh·
@nicklaunches I saw your post, just finished writing on Medium a while ago for this week. Schedule for Saturday morning. I used to describe my story and then Topic i am going to share. People feels relatable. Also add some images that relates to article.
English
1
0
1
9
Ritesh Roushan
Ritesh Roushan@devXritesh·
@alexcloudstar Haha yeah, that first-love MERN bond hits different 😅 Still debugging useEffect at 3 AM like: this is fine 🔥 You still riding the JS wave or secretly plotting your escape?
English
0
0
0
3
Alex Cloudstar
Alex Cloudstar@alexcloudstar·
@devXritesh Hey, everyone's got that first language love, right? MERN can be a wild ride, but it’s the kind you remember fondly (most days). Keep at it, you'll just get better at loving and hating it.
English
1
0
1
4
Alex Cloudstar
Alex Cloudstar@alexcloudstar·
JavaScript developers complaining about JavaScript is peak Stockholm syndrome. "I hate this language but I've built my entire career on it so I guess I love it?" Just admit you're trapped and move on.
English
7
0
11
252
Ritesh Roushan
Ritesh Roushan@devXritesh·
@alexcloudstar Haha yeah, that paycheck-sized pentagram hits different 😈 Worth it tho? (asking for a friend who's still writing useEffect cleanup functions at 2 AM)
English
0
0
0
3
Alex Cloudstar
Alex Cloudstar@alexcloudstar·
@devXritesh Haha, right? It's like we signed a deal with the devil for those sweet paychecks. Guess we're all just code masochists.
English
1
0
1
8
Ritesh Roushan
Ritesh Roushan@devXritesh·
@0xlelouch_ I'm doing everyday, solving at least 2 DSA, Read one article or Topic about system design. Along with building project on weekend. After working hours, managing all of these, waiting for one right chance.
English
0
0
0
37
Abhishek Singh
Abhishek Singh@0xlelouch_·
@devXritesh The path of most resistance, you need to grind early to get lucky
English
1
0
2
242
Abhishek Singh
Abhishek Singh@0xlelouch_·
My friend and I are both software engineers. We are same age. Have similar skill level. We both write backend code. And we both sit in front of a laptop for 8 to 10 hours a day. But one small difference is slowly making his life very different from mine. He earns in dollars. I earn in rupees. At first, I did not think much of it. I used to think, salary is salary. Work is work. Code is code. But over a few years, I understood what was really happening. Every month, he gets paid in USD. When he converts that money to INR, he gets a stronger payout. And when the rupee gets weaker against the dollar, his income in rupee terms rises even if his dollar salary stays the same. That is the part many software engineers in India do not fully understand. When people say: "The rupee fell against the dollar" It simply means you now need more rupees to buy 1 dollar. Example: If 1 USD = ₹80 and later 1 USD = ₹88 that means the rupee has weakened. Earlier, $1,000 = ₹80,000 Now, $1,000 = ₹88,000 Same work. Same client. Same dollar payment. But now the person earning in dollars gets ₹8,000 more just because of currency movement. This is why my friend keeps getting richer in rupee terms without even asking for a raise. Now look at the other side. If you live in India and earn in rupees, a weaker rupee quietly makes many things more expensive over time: - imported gadgets - foreign software tools - international travel - overseas education - dollar-priced subscriptions - even some fuel and inflation-linked costs So while your salary may go up 8 to 10 percent, your purchasing power may not improve much. This is the trap. Many Indian software engineers think: "I got a raise, I am doing well" But if the rupee keeps weakening and inflation keeps rising, you are running hard just to stay in the same place. My friend understood this early. He did not become a genius overnight. He just did 3 simple things: 1) learned skills global companies pay for 2) started working with clients who pay in dollars saved 3) and invested instead of inflating lifestyle That is it. No flashy startup. No rich dad. No lucky crypto trade. Just one decision: stop thinking like a local employee, start building like a global engineer. This is why earning in dollars is not just about a bigger salary. It is about: better currency better savings power better global optionality and faster wealth creation if you stay disciplined Indian software engineers need to understand this clearly: - earning in rupees can make you comfortable - earning in dollars can accelerate wealth - building equity or business can change your life Salary matters. But the currency of that salary matters too. If your goal is real wealth, not just monthly survival, you cannot ignore the dollar vs rupee game.
English
3
2
60
3.9K
Ritesh Roushan me-retweet
Ritesh Roushan
Ritesh Roushan@devXritesh·
The Jevons Paradox states: When a resource becomes cheaper to produce, its demand increases, not decreases. 📉📈 Because AI makes writing functions practically free, startups aren't building less software they are shipping 10x more features. What happens when you have 10x more code hitting production? You get 10x more microservices, infinitely heavier PostgreSQL queries, and absolute chaos in your Kafka event streams. AI writes the logic. But human engineers still have to architect, debug, and scale the massive distributed systems to keep it all from crashing. Are you using AI to write code, or to debug architecture? 👇
Ritesh Roushan@devXritesh

Interviewer: "AI can now write 80% of our boilerplate code in seconds. Doesn't that mean we need fewer software engineers?" Actually, economic history proves we are going to need exponentially more of them. It’s called the Jevons Paradox. What is it, and why is it about to break our infrastructure?

English
1
1
4
90
Mahesh Nani
Mahesh Nani@maheshnani122·
"Build an audience before you build the product" People mock this advice But it's literally why I'm tweeting every day before launch The audience is the distribution. And distribution beats product every time
English
17
3
20
261
Ritesh Roushan
Ritesh Roushan@devXritesh·
@Devinbuild I think post on established account, slowly switch the niche you want. Recently I have started on Instagram page for same as X
English
1
0
0
11
Devin
Devin@Devinbuild·
You have 20k followers on TikTok in a unique niche: Is it better to start a new account in the niche you want to post about or start posting on the established account
English
19
0
21
399
Anas
Anas@Anas_founder·
What’s the function of this in a laptop charger?
Anas tweet media
English
17
0
14
363
Ritesh Roushan
Ritesh Roushan@devXritesh·
The difference between junior and senior Java developers isn’t years of experience. It’s how they think. Junior developers: • Focus on syntax • Write code that works • Google every error • Copy solutions • Think in classes Senior developers: • Think in systems • Design before coding • Optimize performance • Understand trade-offs • Prevent production failures Example: Junior: “Spring Boot API works locally.” Senior: “What happens under 10k requests/sec?” Junior: “Use a library.” Senior: “Understand the internals.” Junior writes code. Senior engineers build reliable systems. That’s the real difference.
English
7
1
16
874
Ritesh Roushan
Ritesh Roushan@devXritesh·
@Devinbuild Yeah it's important stuff when you serving real time data to the users.
English
0
0
0
5
Devin
Devin@Devinbuild·
@devXritesh Infinite scroll is one of those things that looks simple until you realize it’s basically a database problem disguised as UX.
English
1
0
1
5
Ritesh Roushan me-retweet
Ritesh Roushan
Ritesh Roushan@devXritesh·
System Design Series - Community Edition Infinite Scroll: Simple UX, Complex Backend It looks effortless. User scrolls down and new content loads automatically. No page reload. But the backend reality is very different. What actually happens: User reaches the bottom. Frontend sends a cursor to the API. Backend runs a fast indexed query for the next batch. New data appends seamlessly. Most engineers get this wrong: They use OFFSET pagination for infinite scroll. Why it fails at scale: Queries slow down dramatically. Duplicates or missing records appear. Real-time updates break everything. The correct professional approach: Cursor-based pagination. It delivers: Consistent results every time. Lightning-fast index-driven queries. Perfect support for live feeds. This powers every major social feed, product list, and content platform. Rule to live by: Infinite scroll without cursor pagination becomes broken UX at scale. Beautiful frontend always requires solid system design underneath. Tomorrow: Week 1 Recap + Q&A Offset or Cursor pagination? Which one would you choose? Drop your answer below. #SystemDesign #APIDesign #Backend
Ritesh Roushan tweet media
English
9
2
24
309
Ray🫧
Ray🫧@ravikiran_dev7·
Who's gonna be the my 2000th follower 🫣
Ray🫧 tweet media
English
13
3
30
1.5K
Ritesh Roushan
Ritesh Roushan@devXritesh·
@nikitabier Still waiting for Listening features, Summary features will upgrade user experience.
English
0
0
0
28
Nikita Bier
Nikita Bier@nikitabier·
We’re rolling out summaries for Articles now. Just tap the Summarize button if you want to know if it’s worth your time to read it (or if your attention span is 12 seconds).
English
1.2K
251
3.3K
654.3K