Pushpa @codeeTinkerer

India Joined April 2021

Tweets

936
Followers

257
Following

1K
Likes

1K

Pushpa @codeeTinkerer

3 weeks ago

@version0chiro Which season going on

0 0 0 44 0

View Details

What an amazing line from Hanuman ji chalisa 🤌🏻 "Budhi Hin Tanu Janike, Sumirau Pavan Kumar" "Bal budhi Vidya dehu mohe" "Harahu Kalesa Vikar" Meaning: I know I don't know everything. Help me stay humble enough to keep learning, strong enough to keep building, wise enough to make good decisions, and free from the inner habits that distract me from what truly matters.

46 447 4K 93K 580

View Details

Pushpa @codeeTinkerer

9 months ago

Today learnt about securing webhooks with HMAC 1. Create signature: sig = HMAC(secret, JSON.stringify(payload)) 2. Send it in header: X-Signature: sig 3. On receive, recompute & compare: expected === received secret = a shared private key (known only to sender & receiver).

0 0 2 42 0

View Details

Pushpa @codeeTinkerer

10 months ago

@version0chiro 🤣

0 0 0 22 0

View Details

Pushpa @codeeTinkerer

10 months ago

@systemdesignone Playbook

0 0 0 11 0

View Details

Bhagawad Gita @Bhgawad_Gita

10 months ago

13 698 6K 122K 760

View Details

Manu Arora @mannupaaji

11 months ago

That unpaid intern after the final push to prod

19 26 1K 32K 33

View Details

Alcuin Press @AlcuinPress

11 months ago

You can read Carl Jung 100 times and still be blown away at the 101st

98 4K 27K 984K 10K

View Details

neural nets. @cneuralnetwork

a year ago

yesterday’s plane crash shattered something deep within me. not just because lives were lost, but because stories vanished in a moment. a family, scattered across borders, had finally reunited to fly to london. they were just trying to be together. two british tourists, drawn to the soul of india, had spent weeks exploring its culture. they were on their way home. a girl, the first from her village to land a job in london, was heading toward a new beginning. another was simply visiting her nani, carrying nothing but love. and in one instant, all of it ended. we spend our lives making plans, postponing conversations, saving our affection for some later day. but the truth is that we never really know when we’ve said our last hello, our last i love you, our final see you soon. today might be the last time you laugh with a friend, fight with your partner, or hug your mother. we move through life like we’re invincible. we’re not. we’re fragile, perishable, and utterly human. and it is in that fragility that life becomes most profound. not because it lasts forever, but because it doesn’t. it is short, unpredictable, and it asks of us a quiet kind of courage to live fully, love freely, and speak gently while we can. so say it now. call them now. forgive where you can. feel everything. hold the people you love a little tighter. because in the end, what remains is not time, but memory. and memory only lives when we choose to be present before everything slips away. so love like you're running out of time, because one day, without warning, the world will go on and you won’t get to say goodbye.

8 20 260 14K 38

View Details

huss @hussamfyi

a year ago

326 5K 32K 2.1M 6K

View Details

maharshi @maharshii

a year ago

you can just do things, Arjuna.

13 70 1K 57K 130

View Details

Pushpa @codeeTinkerer

2 years ago

board is looking more beautiful day by day

0 0 1 61 0

View Details

Pushpa @codeeTinkerer

2 years ago

@ayushunleashed @ProtagonistO1 @ReelsAiPro perfectly said!

0 0 2 69 0

View Details

Pushpa @codeeTinkerer

2 years ago

Moon and Venus tonight✨🫰🏻

0 0 0 69 0

View Details

Arpit Bhayani @arpit_bhayani

2 years ago

Once I was reviewing a code and I found that at multiple places the joins were avoided in favor of multiple selects ⚡ Upon asking, I got the response - joins are expensive and we should avoid them 🤦‍♂️ This is not true at all. Let me debunk the myth and give you a way to understand the costs involved. Joins are expensive, but only when the data we are joining is huge, or your table lacks the right indexes, or when we are joining a large number of tables (>12). A join query can always be substituted with multiple select statements, but you may end up with an n+1 query problem. Select statements are great but remember every select statement you fire, needs to go to the database over the network and come back to the client. Each query requires connection establishment, query parsing, query execution, disk access, and data transfer. Even if the statement looks simple, the overhead of network roundtrip and query execution over multiple retrievals is substantial; and in most transactional cases will be greater than the cost of a join query. A single join query completes the same task in a single shot. Thus one round trip, one-time query parsing, query optimization, and execution and you get the intended result. Coming back to the incident, we replaced multiple select with a join and the response time of API was reduced from 1.2 seconds to 152ms. Pretty amazing. Again, this is contextual to the data we had and the use case we were solving. So, instead of blindly following some tips and advice you hear on the internet, it is better to benchmark it on your own codebase and pick the better one. Beware when someone says such generalized statements; take them with a pinch of salt. Knowing the nuances makes you a better engineer. ps: admissions open for sys design feb cohort - arpitbhayani.me/course #AsliEngineering #SystemDesign