SAHIL SRIVASTAVA

[SAHIL SRIVASTAVA @Sahil250199]

Twitter done, what's next Amazon, Google or Meta. Top firms are in danger now hypothesising the fact that Elon's wealth is growing at an unbelievable rate.

Welcome to decentralisation, @elonmusk can we expect the Twitter code to be open source now?

#TwitterTakeover

[SAHIL SRIVASTAVA @Sahil250199]

If you are looking for challenging problems like production incident problems, repository based coding problems, concurrency based issues that we face in our day to day job do checkout the platform. https://t.co/pKvYqRYVRl

[SAHIL SRIVASTAVA @Sahil250199]

I am glad to share with you all that we have crossed 250+ users within a week on Gronex.

There are some really positive feedbacks that I have received about the platforms, as well as some constructive feedbacks also which is helping me to add more features and improve the ones.

[SAHIL SRIVASTAVA @Sahil250199]

Two threads raced applying the same domain effect twice in at-least-once message processing.

How do you safely reserve, retry, and dead-letter without duplicates?

https://t.co/QQqa2HNaAq
#Concurrency

[SAHIL SRIVASTAVA @Sahil250199]

Two parallel releases on a held escrow can double-payout funds silently.
How do you prevent overlapping state changes in time-gated auto-releases?
https://t.co/3wmE3tdfD9
#Concurrency

[SAHIL SRIVASTAVA @Sahil250199]

Two simultaneous earn callbacks can double-credit points if idempotency isn’t airtight.
How do you guarantee single-credit even when retries race?

https://t.co/i1MH76a1Wl
#backend

[SAHIL SRIVASTAVA @Sahil250199]

One off-by-one check lets a Kanban column accept too many cards and breaks flow.
Can you crack enforcing WIP limits without dropping cards or losing order?
https://t.co/K8svuJmVq0 #backend

[SAHIL SRIVASTAVA @Sahil250199]

Tenant cross-contamination in rollout selection caused cascading failures.
How do you enforce strict tenant fleet isolation and halt by failure rate?

https://t.co/KxUXcMVm58

#IoT

[SAHIL SRIVASTAVA @Sahil250199]

Two claims hit for the same incident & payout math skipped deductibles—coverage was mismatched by date, causing wrong approvals. How do you ensure incident date coverage integrity?
https://t.co/exCxBQM3Un #backend

[SAHIL SRIVASTAVA @Sahil250199]

Two requests hit the same room and dates simultaneously—double bookings happen silently. How would you lock to prevent this without deadlocks?

https://t.co/UHvepsx5ug
#Concurrency

[SAHIL SRIVASTAVA @Sahil250199]

Two guests book last room with overlapping dates — but back-to-back stays break silent availability rules. How do you fix half-open interval overlap checks?

https://t.co/gMKYeAxRxN

#backend

[SAHIL SRIVASTAVA @Sahil250199]

Two requests hit this repo simultaneously and broke order status history with duplicate events.
How do you enforce only exact next-step transitions?
https://t.co/5Ry1plzgCr #backend

[SAHIL SRIVASTAVA @Sahil250199]

Two buyers snag the last item simultaneously—inventory oversold and alerts silent.
How do you lock purchases to stop race conditions but keep speed?
https://t.co/t0pTy6D5QZ
#Concurrency

[SAHIL SRIVASTAVA @Sahil250199]

Unearthing the unseen bug: unstable user bucketing broke rollout consistency. Priority order and environment isolation matter more than you think.
https://t.co/BV58JGqcPh #backend

[SAHIL SRIVASTAVA @Sahil250199]

This 30-line backend logic lets two concurrent spends overshoot the daily and total budgets.

How do you safely record spend and pause campaigns without double-charging or race conditions?

https://t.co/XyDZ45wQcp

#Backend

[SAHIL SRIVASTAVA @Sahil250199]

Two threads finalizing identical content can create two stored files instead of one. This breaks dedup guarantees under concurrency.
How would you prevent this race?
https://t.co/O7G0PjUbPD #backend

[SAHIL SRIVASTAVA @Sahil250199]

Same cart, simultaneous coupons: cart total goes negative. How do you correctly cap discounts and fix stacking? What ordering yields a fair price?

https://t.co/eK7gztawhi #backend

[SAHIL SRIVASTAVA @Sahil250199]

Two nodes raced to grab a job lease milliseconds apart—both ended up running the same job. How do you prevent stale owners from hijacking work after lease expiry?

https://t.co/5P2cdy27BX
#Concurrency

[SAHIL SRIVASTAVA @Sahil250199]

The scariest SLA bugs quietly misclassify tickets as on time.

This system mistakes >= for > and re-stamps timestamps, breaking breach detection.

What subtle fix keeps SLA reporting airtight?
https://t.co/yWIB1OZbEX #backend

[SAHIL SRIVASTAVA @Sahil250199]

CRM lead assignment needs precise eligibility checks, deterministic tie-breaks, and exact load accounting—skip these and your system’s lead distribution breaks. Fix the bugs hands-on: https://t.co/iIwuLOffnT

[SAHIL SRIVASTAVA @Sahil250199]

Spot the bug: Bank Account Transfer and Deadlock Prevention System

Repo debugging challenge:
fix locally, run ./verify.sh, compare solution.

https://t.co/XznegwTNNy