Utpal Sen

148 posts

Utpal Sen banner
Utpal Sen

Utpal Sen

@utpalXsen

i wish i was where i was when i wished i was here

prison Katılım Mart 2015
0 Takip Edilen2 Takipçiler
Sabitlenmiş Tweet
Utpal Sen
Utpal Sen@utpalXsen·
ai has sucked all the fun out of programming
English
0
0
1
203
Utpal Sen
Utpal Sen@utpalXsen·
modern sql joins aren't just for tables anymore. you can use LATERAL joins to run a "for-each" loop per row (like getting top 2 orders per user). you can even use CROSS JOIN UNNEST to explode a json array trapped inside a single column into queryable rows.
English
1
0
0
8
Utpal Sen
Utpal Sen@utpalXsen·
what is a sql join? most people learn joins using venn diagrams. but venn diagrams are a lie. they show intersections, but sql joins actually multiply data. a join is fundamentally a cross product followed by a true/false filter. here is how they really work.
English
1
0
1
10
amrit
amrit@amritwt·
this is what I wanted wispr flow to be like
English
14
5
274
13.9K
Ghanshyam Singh
Ghanshyam Singh@https_ghanshyam·
Since the morning i confused between should I need to buy claude pro or not??
English
6
0
5
1.2K
Utpal Sen
Utpal Sen@utpalXsen·
it's a great lesson in systems design. we instinctively throw concurrent threads at scaling problems which usually just introduces race conditions and lock overhead. sometimes the most scalable architecture is just a single thread that never ever blocks.
English
0
0
0
22
Utpal Sen
Utpal Sen@utpalXsen·
the true bottleneck in most systems isn't the cpu, it's waiting for network or disk. redis avoids disk by keeping the dataset in memory and avoids network blocking by making all sockets non-blocking. it just drains the ready queues at raw memory speeds.
English
1
0
0
25
Utpal Sen
Utpal Sen@utpalXsen·
i was learning today about how redis sustains millions of tcp connections on a single thread. everyone assumes you need massive thread pools to scale i/o. it's completely backwards. the mechanics of why one thread wins are actually beautiful.
English
1
0
0
28