Ankit varshney (@Av1theking) header
Ankit varshney (@Av1theking) profile picture

Software Engineer @ https://teapawt.net/t.co/E0mcuQ4aaE

Joined October 2023
I published a benchmarking suite for Effect, and it crossed 1k downloads 🙂 Use it to benchmark your code. It’s built for agents.
1
1
14
271
What a wonderful API response for HTTP 200 status it is
1
7
380
Built an Effect lib for postgres CDC (change data capture)
1
1
9
286
Shipped pg-replicator: an Effect-native PostgreSQL logical replication client. npm i pg-replicator
1
12
328
Implementing Electric Sql postgres Sync
8
298
holy banger @EffectTS_ this is such an important building block and you usually end up building this yourself or using something too opinionated effect.website/docs/v4/api/e…
17
24
7
611
62,983
Tried implementing MVCC (Multi Version Concurrency Control) from first principles
2
15
760
Ok yeah I can say now AI has increased my productivity atleast by 4x
14
1,323
Ankit varshney retweeted
This will piss you off but it's true
111
158
84
2,585
371,558
After so much procrastination I have finally implemented Google's mapReduce research paper in go github.com/AVtheking/MapRedu… Things I have implemented: - User defined Map and Reduce functions. - Master handling states of all the tasks, worker executing map/reduce tasks. - Storing of intermediate results from Map task to local disk partitioned into R regions. - Atomic writes by first writing results to temp file and then renaming file. - Task timeout, Task ownership, stale completion rejection using workerId+ epoch. - Handling duplicate executions. - gRPC server between master and worker(still single-process for now). Though it is not a complete implementation of the paper as I have left some parts like -> separate processes, combiner, sorted output, input splitting, backup tasks. I used AI to help me breakdown tasks, review my approach, roast me, help in understanding things.
7
311
It's funny that we recently encountered same concurrency problem which was asked from me in Interview 🙂. When we identified the core problem the solution was easy since we already know a solution for it, but the hard part was to identify what exactly an issue is, which took around 4 days
4
226
Why are you doing this to me @graphite ?
2
228
2025 was a fun year for me Contributed quite a bit in Open source mainly in @aisdk and @llama_index Joined an ambitious startup and started my first full time role :) Learned a ton. Excited for more growth in 2026
1
9
412