tridip

22, Engineer. learning obsessively & chasing gains.

[Saikat @Saikat_deb12]

Small steps, steady progress🚀

React exercises
Upsolved few from CF-1133
Virtual contests with @tryindeep & @always_VinodKr

Some thoughts...
Spent most of college learning alone and always wished for like-minded peers

Now, solving and discussing prob together feels unreal😅

[tridip @tryindeep]

Day 23 #100DaysOfCode | 11.11.26

Due to Bhaidooj not able to work on anything today.

Still appeared on DSA contest on AtCoder.
- completed 2/4 questions.

will comeback hard tomorrow

[tridip @tryindeep]

Day 22 #100DaysOfCode | 10.11.26

Data Structures and Algorithms
- frequency arrays (5 problems)
- set & maps (6 problems)

Development :
- React hooks (useState, useEffect).
- Practicing some problems on it

[tridip @tryindeep]

@avrojit_dutta yep, zepto.

[tridip @tryindeep]

Happy Diwali to everyone 🌼

[Saumya Verma @nikkuv5787]

500 chips of summer

[tridip @tryindeep]

India's AQI map looks like a Holi celebration, except the colours represent air pollution. 💀

[tridip @tryindeep]

We know that there are 3 version of this project :

v1 - only using Database call (reliable but slow)
v2 - in memory (fast but not reliable )
v3 - using scale HTTP and WS with queue and Engine. (fast and reliable)

[tridip @tryindeep]

Happy Diwali Everyone✨🔱

Day 21
Today's learning

Build Mini Kalshi - Prediction Market (Backend)

- Completed all the endpoints
- wrote all test cases

GItHub : https://t.co/5odzEPZjGJ

[tridip @tryindeep]

If the headline/title is a question instead of a statement, the answer is "no".

[tridip @tryindeep]

Day 20 #100DaysOfCode | 07.11.26

System Design (revision):

- Monlith and Microservices Architecture
- Database Sharding (tough).
- caching

Gsoc :
Selected some orgs for my tech stack.
Check there code selected 3 (2 primary 1 backup).

[tridip @tryindeep]

Day 19 of #100DaysOfCode | 06.11.26

Building "Mini kalshi" update

Writing code without ai, society will accept me?

> Working on place order endpoint,more than 600+ lines (not completed).
> Completed test for split and merge endpoint

DSA
> 3 difference array questions.

[tridip @tryindeep]

Day 18 of #100DaysOfCode | 05.11.26

DSA

- learned Prefix sum techniques.
- 7 question solved.

System Design (revision):

- vertical and horizontal scalling
- decoupling, master slave archi overview
- load balancing
- consistent hashing
- message / task queue

#BuildInPublic

[tridip @tryindeep]

@Saikat_deb12 @gkcs_ step by step!

[tridip @tryindeep]

Reached 100 followers. Thank you everyone.

[tridip @tryindeep]

Day 17 learning everday

DevOps
- ec2
- ngnix
- reverse proxies PM

DSA
- 7 sub array assignment question solved!

#BuildInPublic #DevOps

[tridip @tryindeep]

Day 16 building with @Saikat_deb12

Backend Mini kalshi
- created test for some routes.
- discussed whole createOder controller.
- around 20 edgecases we have to take care.

Whenever makes any changes in controller that effects the schema. Working on it.

Class :
- Reacthooks.

[tridip @tryindeep]

@DigvijayShelke6 haha, it's prediction market.

[tridip @tryindeep]

Strengthening my Mini-Kalshi backend.

- Wrote Register & Login tests using Bun + Axios.
- Tested input validation, duplicate users, password security and authentication flows.
- Fixed a role-assignment security issue.

Learning TDD methond!

[tridip @tryindeep]

@Saikat_deb12 @kirat_tw @100xDevs This helped me understand that schema design should come from the system's requirements and data flow, rather than just creating tables first.

Now I have a much better understanding of why the Mini Kalshi needs entities like Orders,Trades/Fill,.Overbrook how they should interact

[tridip @tryindeep]

Before building the **Mini Kalshi**, I realized I first needed to understand **why we are designing the schema the way we are** and how a real exchange system works.

So I went through a system design lecture on CEX/order-book architecture.

What I Learned : 👇

[tridip @tryindeep]

@Saikat_deb12 @kirat_tw @100xDevs Dif approaches to building an Order Book:

1. Store everything in the DB
But slow for high-frequency operations
In-memory Order Book

2. Extremely fast
But not reliable by itself because memory can be lost

3. Scalable architecture
In-memory processing
WebSockets
Queues
HTTP APIs