Samarkun

Redesigned my centralized exchange (CEX) architecture today 🚀 Benefits : I will code the match engine in Rust ,which make its so fast and spawn a thread for every market Added: • Microservices • Risk engine • Event-driven queues #systemdesign #fintech #web3 #buildinpublic

@noor36758 Production code crash

I'm a backend dev, scare me with one word

Taking note of everyone who presses this button

Just won the $3000 grant !!!! thank you @SuperteamIN & @SolanaFndn super happy today , as this is a huge milestone for any Web3 dev grinding hard, and I’m proud to be part of such an amazing community <3 massive shoutout to @paarugsethi for all the backing !!

Guys i build a chess game fron scratch

Built a Chess game from scratch ♟️ • Full chess board UI • Turn-based gameplay • Move tracking for both players • Captures and game state sync Working on adding checkmate detection and real-time multiplayer next. Building real projects every day 🚀 #buildinpublic #webdev

Do not keep looking for beginner-friendly content, because for harder topics, there is none. Also, they often optimize for feeling smart rather than becoming smart. Try to build a habit of reading, watching, and absorbing detailed information and concepts. This will not only help you move away from being spoon-fed, but it will also make you better at abstract thinking. I believe abstract thinking will become crucial in the coming decade, as the world shifts toward solving more complex and ambiguous problems that are not easily visualized and comprehended. We are seeing an early sign of the drift with you-know-what. Extrapolating from here, I would say it is going to be increasingly vital for us to think beyond the obvious. The people who will navigate that well are not the ones who found the best beginner guide. They will be the ones who learned to sit with the hard stuff until it made sense.

@arpit_bhayani Congrats sir ji ! youtube kuch ho jaye ab

Joined Razorpay as Principal Engineer II :) From being a long-time customer to now building parts of the system - it's a full circle. Fintech is a new territory for me - time to get under the hood of how money actually moves. New domain, same guarantees - availability, correctness, performance - just with real money on the line.

Built my first basic crypto bridge today 🌉 • Lock tokens on Chain A • Listen to Deposit events using getLogs • Trigger actions off-chain • Preparing to mint on Chain B Learning how real bridges like Wormhole actually work under the hood. Web3 getting real 🚀 #web3 #ethereum

@kirat_tw Currently I am using a nvim . I don't use ai in my learning face . When I need urgent work than i use ai but not day to day coding bec i think if i know the tec very well or stack very well and syntex also then i cursor there and and generate the code there .

Curious how has coding changed for you in the last ~1 year. Is anyone using VSCode anymore? Cursor? Claude code? How much of your day is spent coding vs prompting. What do you do when the AI is coding? Do you parallelly start multiple tasks? Are you more productive?

@hirvesh @Habit_Pixel It's really looking cool and polished dude, specially that single habit widget .

First video update after a while for @Habit_Pixel 😅 A bit rusty but I talk about a new widget type for iOS and supporting iOS 26 Clear & Tinted modes for widgets 👇

If you finding a greate habit tracker that is visible to your screen , checkout guys it's really helpful bec its just visible to your screen and when ever you open a screen your tasks should be there .

So guys I learn how you can transfer assest from different block chains ex : ETH -> POL / SOL . I am going to write a code for centralized bridge. I you also want to know how bridges work see here

To go back: Burn the wrapped tokens → unlock the original tokens. Two main mechanisms: • Lock & Mint • Burn & Unlock Also learned about centralized vs decentralized bridges and why they are one of the most complex parts of Web3. Building a simple EVM bridge next 🚀 #web3

Today I learned how crypto bridges actually work 🌉 A bridge doesn’t really “transfer” tokens between blockchains. Instead it works like this: 1️⃣ Lock tokens on Chain A 2️⃣ Mint wrapped tokens on Chain B Example: 100 SHIB on Ethereum → lock them → mint 100 wSHIB on Polygon

◢ ▊▊▊◤ ◥ ▊▊▊◣ ◢ ▊▊▊◤ ◢ ▊▊▊◣ ▊ ▊ ◥ ▊▊▊◤ ▊ ▊ ◥ ▊▊▊◣

lock in.

Guys i am currently start improving my design taste I am a dev so i don't have that much knowlege that how my web app looks good I don't need to master design but I am able to make a decent design of my web app that a goal I post a desing regurally . What you are working on ?

Yes, when the active node goes down, the passive (backup) node takes over - but how exactly? How are they configured? BTW, this is where keepalived comes in. Let's dig deeper into the nuances. Keepalived is used to create a virtual IP. This IP automatically follows your healthy instances, and clients use this virtual IP to connect to the healthy instance. Keepalived implements the VRRP protocol, where multiple instances share a virtual IP address (their actual IP addresses would be different). The instance with the highest priority becomes the master and owns the VIP, while the others stay as backups (passive). After configuring keepalived, the master node sends heartbeat advertisements every second to the multicast IP, and backup nodes listen for these packets. When the master fails, the backup detects silence after ~3 seconds and promotes itself, moving the VIP instantly. When a failover occurs, the new master announces that it now owns the virtual IP, updating all switch MAC tables immediately. Clients connecting to the VIP seamlessly reach whichever instance is currently healthy. Thus, your load balancer or clients always connect to the same virtual IP regardless of which physical instance is serving - no DNS changes, connection resets, or manual intervention during failures. So, three important keywords here - virtual IP, VRRP, and keepalived. Use your favorite LLM to dig deeper into the configuration and actually see seamless failover in action.