Keshav Mishra

✅ Automate system utilities with a powerful CLI interface Built with JavaScript (Node.js) as part of Thunder Hackathon 3.0. Learning, building, and pushing my limits one project at a time. 🔥 #NodeJS #JavaScript #Hackathon #ThunderHackathon #BuildInPublic #100DaysOfCode

@KunikaKishore Interested

Amazing #opportunity as Software Engineer, offering ₹10- 15 LPA at #Hyderabad !!

Day2 of learning backend from @rohit_negi9 Finally understood the difference! require() = CommonJS (Node.js default) import = ES6 Modules(Modern JS) Important points: require() - synchronous, dynamic import - asynchronous, static #daysofcode #BuildinPublic #webDevelopment

@nitesh_singh5 Interested

Role - Full Stack Developer Intern Stipend - 25K - 50K per month Experience - Freshers - Develop, maintain, and enhance company's web app - Assist in website optimization, bug fixing Let us know if you are Interested 👇

Day 1 Introduction to backend by @rohit_negi9 Understanding: Why do we need backend? How data is flow from Client to Server Creating First server -> request & response #thunder #100daysofcode #WebDev #BuildInTheOpen Waiting for Todays Session

Day 16 of Thunder - Memory Management in JS by @CoderArmy and @rohit_negi9, learning how js code is execute behind the seen in ram (memory allocation & code execution phase). Address are store in stack memory is allocate in heap. Solve 2 leetcode problem. #100DaysOfCode #WebDev

@hemanttbuilds @X Lets connect

Hey @X algorithm I'm looking to connect with people interested in: → Frontend → Backend → Full Stack → DevOps → LeetCode → AI/ML → Data Science → UI/UX → Freelancing → Startups Say hi & let's grow together 👋

@CoderArmy hackathon result

AWS’s Jeff Barr: Developers are moving from writing code to directing AI agents.

✅ Automate system utilities with a powerful CLI interface Built with JavaScript (Node.js) as part of Thunder Hackathon 3.0. Learning, building, and pushing my limits one project at a time. 🔥 #NodeJS #JavaScript #Hackathon #ThunderHackathon #BuildInPublic #100DaysOfCode

Introducing NEXUS Sentinel System Monitor A Node.js based System Intelligence & Automation Suite that can: ✅ Collect detailed system information ✅ Generate structured JSON reports ✅ Manage code files with CRUD operations ✅ Monitor system health & network

@CoderArmy Go to youtube search DSA playlist by rohit negi and watch every single video without any questions only 163 which make master in dsa and programming

If you had to start your coding journey from Day 1 again. What's the ONE thing you'd do differently? 👇🏻Let's help the next generation of developers.

@CoderArmy Rules: Every Coder think about System Design. Everyone must know how to think from first thought principal

I think we need "Coders Janta Party" 🙂

Day1 - Just Completed Thuder Class 1 & Slove 3 DSA question from @striver_79 SDE sheet DSA question are from topic Binary Tree first one Inorder Traversal (LNR) second one Preorder third one is PostOrder #dsa #striver #sde

@CoderArmy How bhaiyaa

Job market too crowded, Let’s generate our own openings

@CoderArmy Thank you bhaiyaa I'll definitely add this

@keshav0774 Awesome I loved the UI one thing you can add in your portfolio is add a Why should you hire me? section and give it some thought and add content accordingly trust me it is a useful thing

Developers, drop your portfolio websites 🙌🏻 I will review them and give honest ratings 🙂

@CoderArmy Bhai ey course kb tak complete ho Jaye gaa

We are Launching Full stack web Development course in 2026 from basic to advance level. We cover web Dev , system Design, Security and DEVOPS. - Course Link: strikes.in/course/thunder… - Start Date: 1 June 2026 - Class Timing: 9pm (Mon, tue, thu, fri)(Live) [Recording will be available after the Class] Watch Full Video for more details: youtu.be/TzQpD3EgyDo?si…

@HarshJain_Coder Bhai mere ko bhi ey shuru karna hai kaise shuru hoga I mean dsa ata hai but ey konsa platform haii

Today's log: - 2x 1500 rated problems - 1x 1400 rated problem - 1x leetcode POTD Had to go to college today for some time, then slept in the afternoon 😅

@adityatandon02 Bhaiya mera ek question haii rate limiting ko leke

Why Network partition are inevitable in System Design ? When a system runs on a single machine, life feels simple. There is one source of truth, one network boundary, and almost no ambiguity about where data lives or how it is accessed. But the moment a system becomes distributed, spread across multiple machines, racks, regions, or even continents, something fundamental changes. Communication is no longer guaranteed. And that is exactly where network partition enters the picture. A network partition happens when a group of nodes in a distributed system loses the ability to communicate with another group. The nodes themselves are still alive, still processing, still holding data, but the “network glue” that keeps them in sync breaks temporarily. From the system’s perspective, this is not a rare edge case , it is a natural consequence of operating over unreliable networks. If you think about how modern systems are built, data is constantly moving across machines through switches, routers, load balancers, and cables. Each of these components introduces a probability of failure. A cable can disconnect, a router can misroute packets, a cloud zone can go down, or latency can spike so high that nodes assume each other are unreachable. Even software issues like GC pauses or CPU throttling can mimic network failures by delaying responses long enough to trigger timeouts. In such an environment, expecting perfect communication is unrealistic. Before a partition, all nodes appear synchronized. Data is replicated, requests are routed smoothly, and the system behaves like a single logical unit. But once the network splits, the system is effectively divided into isolated islands. One group of nodes can no longer see updates from the other. Now the system faces a critical decision, should it continue accepting requests independently in each partition, or should it stop operations to avoid inconsistency? This is where the inevitability becomes more apparent. Distributed systems cannot prevent partitions, they can only decide how to behave when they occur. This tradeoff is formally captured in the CAP theorem, which states that in the presence of a network partition, a system must choose between consistency and availability. Either you ensure all nodes see the same data (consistency) by rejecting some requests, or you keep the system responsive (availability) by allowing divergence in data. In real-world systems, partitions are not just theoretical. Large-scale systems frequently experience partial outages, one region becomes unreachable, a subset of services times out, or cross-data-center links degrade. Systems like distributed databases, message queues, and microservices architectures are all designed with the assumption that partitions will happen. Techniques like leader election, quorum reads/writes, replication strategies, and eventual consistency exist specifically to handle these scenarios. Another subtle reason partitions are inevitable is scale. As the number of nodes increases, the probability of some subset failing to communicate grows significantly. What might be a rare event in a small cluster becomes a routine occurrence in a large distributed system. This is why companies operating at scale design for failure as a default assumption rather than an exception. Happy designing ❤️

@rohit_negi9 Bhaiya ek course thi complete ho Jane do

High level Design course shoot is tomorrow… GuruJi is ready… It is coming free on youtube…. Any suggestions for marketing…… Best suggestions on comment will get cash price of 1000 💰

Day 34 of learning web dev by @rohit_negi9 bhaiya Solving 2 DSA question Build a mini project stop watch using react js. #Consistency #Web3Community #LearnInPublic #reactjavascript #XCSSProtectJunhui