Backend-Focused Full-Stack Developer | GenAI
Joined July 2024
- Tweets6.3K
- Following684
- Followers717
- Likes22K
I've been wanting to understand what happens beyond writing code how applications actually run and get deployed.
Starting my Docker & Kubernetes journey with this course by @Hiteshdotcom sir and @techie_piyush sir.
Excited to learn and build along the way.
@nirudhuuu
GPS doesn't directly measure distance.
It measures time. 🛰️
And turning tiny timing differences into your location is one of the cleverest tricks in modern technology.
Here's how it works 🧵
And here's the Einstein connection.
GPS satellites carry atomic clocks.
Relativity makes their clocks tick at a different rate from clocks on Earth.
Without corrections, positioning errors would grow by kilometres per day.
One failed database operation can leave an order half-created.
I tested this with PostgreSQL + Prisma today.
Created an order.
Created its items.
Updated stock.
Then I deliberately threw an error.
What happened next? 🧵
But there's another catch.
A transaction alone doesn't automatically prevent every race condition.
If 2 requests try to buy the last item, both might read stock = 1 before either updates it.
Production code needs concurrency-safe stock updates, not just a transaction.
I deleted one index from a 100k-row table.
Query time: 0.13ms → 5.3ms.
Then I deadlocked my own database on purpose.
Day 2 of my PostgreSQL backend lab: 5 lessons on what happens when requests collide 🧵
The fix is simple:
Lock resources in a consistent order.
Both transactions:
Product 1 → Product 2
No circular wait → no deadlock.
Sorting IDs before acquiring multiple locks is one practical way to enforce this.