How I shared my Claude code with my team (kind of multiplayer AI)
I logged into Claude Code on an @instabox_sh machine and gave it access to github and tools we use, created a Slack bot with Socket Mode, and let that bot run a Claude session for each thread on that VM.
Added the bot to our Slack workspace. Now anyone on our slack can just tag @itank to use my Claude code. It builds context from the thread messages and work from that.
1
4
53
Shipped pg-replicator: an Effect-native PostgreSQL logical replication client.
npm i pg-replicator

ALT TypeScript snippet. A pg.Client in replication mode is wrapped with PgReplicator.fromPg. repl.startReplication is called with a slot name, start LSN, publication and protoVersion 2, returning an Effect Stream. Stream.runForEach matches each PgOutput message: Insert, Update and Delete log the decoded rows, Commit calls repl.ack with the commit's end LSN, and Begin, Relation, Keepalive and Unknown are ignored.
1
12
336
Ankit varshney retweeted
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…
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
315
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
227













