@heapofstack

making mistakes and learning. Nonchalant Nerd.

 India
rahulsaini.dev
Joined March 2024
  • Tweets207
  • Following230
  • Followers12
29Media
I want to get back to gaming sooo baddd
19
Great Architecture are always Simple.
30
Rahul Saini retweeted
ohshin
@ohshinbhatJun 15
we live in an era where the desire to be noticed for doing something is greater than the desire to actually do it
28
32
6
393
15,197
Have some good observability and monitoring for your servers for god sake
62
101
236
22
2,814
84,210
Rest Easy, Danya ♥️
34
413
45
5,096
131,785
Last stage of distro hopping
53
Rahul Saini retweeted
BCCI
@BCCI28 Sep 2025
𝗖. 𝗛. 𝗔. 𝗠. 𝗣. 𝗜. 𝗢. 𝗡. 𝗦 🏆 A dominant performance capped by an unbeaten campaign 💪 Congratulations to #TeamIndia on winning #AsiaCup2025 🇮🇳 🥳 Scorecard ▶️ bit.ly/INDvPAK-ASIACUP-FINAL… #Final
2,665
12,291
755
88,951
5,599,128
Supposed to be a better developer now. Let's see
41
Simple code, High Performance is all you need.
43
Corporate life requires an ass-licking skillset I simply wasn’t born with.
717
28,871
3,032
160,971
8,261,724
Rahul Saini retweeted
Тsфdiиg
@tsoding17 Aug 2025
90
313
41
4,700
147,707
Backend development often feels like one big DSA problem — success lies in choosing the right data structures and algorithm.
50
At some point in their career, devs forget they're "engineers" and start role-playing "Frontend Engineer", "Backend Engineer", etc. This is all programming. You can do this all. Doesn't mean you have to master it all. Be good at many things. Be an expert in a few.
Gergely Orosz
@GergelyOrosz5 Jul 2025
"Hiring pure backend engineer and expecting them to do non backend stuff IMO is wrong" Sigh. Any capable intern/new grad picks up whatever new technology is needed to get the job done. If you, as an *experienced* engineer, refuse to do so: you're less capable than an intern
79
149
28
1,595
132,209
OOP SUCKS
44
Don't get attached to a company Get attached to your growth
77
Rahul Saini retweeted
Guillermo Rauch
@rauchg7 Feb 2025
A broken software architecture can’t be fixed with pretty pixels. Design is how it works, not what something looks like.
42
86
20
930
72,067
Stay away from this conditional rendering pattern in react {Boolean && <Component/>} If Boolean is false, React still processes <Component /> but returns false instead of null which might still cause effects or rerenders in some cases
2
81
Always use {Boolean ? <Component/> : null } which explicitly returns null ensuring no rendering or effects
62
In my case I figured this beacuse of one extra API call the dialog box was still getting rendered and causing the extra API call
71
Load more