Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Yash Saini
I'm single, but my "ask her out" keeps helping strangers propose
A few years back I built a small website for fun. I wrote a blog about it, lots of people forked it, and a lot of people actually used it to propose their love. I still don't know how those stories ended, but I like to think the website did its job. Now let me confess something. I never built it because I was a hopeless romantic. It was trending, I needed a project, and "ask her out" sounded fun. And the funniest part? I'm the guy who built a proposal website and never got to use it.
I Built My Friend a Mock Interviewer That Read His Rust Code
This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What I Built grill is a mock technical interviewer that has read your code. It runs in a terminal, on an open model, on your own laptop. I built it for my friend Akash. He has spent the last year writing Rust, ships TypeScript on the side, and is looking for a full-time role. The rounds he dreads are the Rust and JavaScript deep dives.
Dev log #24 Hardening the p2p stack: From flaky tests to WebSocket fixes
Hi, glad you found your way here. I'm Yash, a developer who contributes to open source, mostly p2p networking and AI tooling. Each week I write up what I shipped, what broke, and what fixing it taught me. GitHub · X · LinkedIn · Portfolio TL;DR If you've ever had a CI run fail because a test expected a packet to arrive in exactly 200ms, you know my pain this week.
Dev log #23 Polishing the stack: Diagrams, async shutdowns, and a whole lot of code reviews
Hi, glad you found your way here. I'm Yash, a developer who contributes to open source, mostly p2p networking and AI tooling. Each week I write up what I shipped, what broke, and what fixing it taught me. GitHub · X · LinkedIn · Portfolio TL;DR This week was all about clarity—both in the code and how we explain it. I spent a significant chunk of time in the docs and refactoring event flows, while also diving deep into code reviews for the C# libp2p ecosystem.
Dev log #22 Tearing out the old: Deleting 3,800 lines of legacy p2p code
Hi, glad you found your way here. I'm Yash, a developer who contributes to open source, mostly p2p networking and AI tooling. Each week I write up what I shipped, what broke, and what fixing it taught me. GitHub · X · LinkedIn · Portfolio TL;DR There is no feeling quite like watching a PR diff show thousands of red lines and only a handful of green ones. This week was all about that catharsis.
Dev log #21 Hardening WebRTC-Direct and solving SCM leaks
Hi, glad you found your way here. I'm Yash, a developer who contributes to open source, mostly p2p networking and AI tooling. Each week I write up what I shipped, what broke, and what fixing it taught me. GitHub · X · LinkedIn · Portfolio TL;DR This week was all about the "glue" that holds distributed systems together. I spent my time jumping between the Python implementation of libp2p and a Go-based agent orchestrator.
The receipt should come from the person who received it
This is a submission for Weekend Challenge: Generosity Edition What I Built Every donation platform proves the same single fact: money left your account. The fact you actually care about is the second one, that it reached a person, and the receipt for the first is issued by the organisation holding the money. The thing you're trusting and the thing producing the evidence are the same thing. Cairn changes who issues the receipt. You lock SOL in an escrow no intermediary can open.
Dev log 20: Deleting 180k lines and chasing socket leaks: A week in the OSS trenches
Yash K Saini — Engineer, building in public — AI/ML, low-level (Rust/C/C++), and open source. GitHub · X · LinkedIn · Portfolio A massive week of cleanup and deep technical dives. From deleting 180k lines in my vault to fixing socket leaks in libp2p and contributing to the Rust compiler, I hit 102 commits and a perfect 7-day streak. TL;DR There is something incredibly therapeutic about a net-negative week.
Dev log #19 WebRTC v2 flows, agentic orchestration, and a perfectly synced vault
This week was a high-output sprint across the stack—from low-level p2p networking in Python to refining agentic workflows in TypeScript. I pushed 53 commits and opened 13 PRs, maintaining a perfect 7-day streak while balancing deep protocol work with personal knowledge management. TL;DR I didn't really intend for this to be a "build everything" week, but that’s exactly where the momentum took me.
Dev log #18 From Redis Brokers to Knowledge Graphs: A 177-Commit Sprint
Hit a perfect 7-day streak this week, shipping 177 commits across systems architecture and personal tooling. Between hardening Redis brokers and fixing terminal hijacking in tmux, I managed to push nearly 7k lines of code across eight different projects. TL;DR There’s a specific kind of satisfaction that comes from a perfect 7-day streak where the flow state just doesn't quit.
The test was green. Every real connection would have failed.
This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry. The setting WebRTC-Direct in libp2p has a neat trick for connecting without a certificate authority: the peer's multiaddr contains a hash of its TLS certificate — /webrtc-direct/certhash/<...>. When you dial, the DTLS handshake presents a cert, you hash it, and you check it against the certhash in the address. No CA, no trust store — the address is the pin.
The /sdp endpoint that trusted its callers: fixing a memory-amplification DoS in py-libp2p
This is a submission for DEV's Summer Bug Smash: Clear the Lineup powered by Sentry. Project Overview py-libp2p is the Python implementation of libp2p โ the peer-to-peer networking stack that underpins IPFS, Filecoin, and Ethereum-class nodes. I've been working on its WebRTC-Direct transport, which lets two peers connect without a certificate authority: the peer's multiaddr carries a hash of its TLS cert, and the DTLS handshake is verified against it.
One rented /24 could eclipse a Kademlia node. Now it takes ten.
This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry. The setting py-libp2p speaks Kademlia — a distributed hash table where every node keeps a routing table of other nodes, bucketed by how far their IDs sit from its own. You find a peer or a record by asking the nodes closest to the target, who point you closer, and closer, until you arrive. It's elegant, and it works because of one quiet assumption: the peers in your routing table are a fair sample of the network.
Dev log #17 From 16-bit TUIs to p2p Hardening: A 227-Commit Week
A high-output week focused on shipping GitBanner 1.3.0, hardening WebRTC and DHT layers in py-libp2p, and archiving kad-monitor with a proper demo harness. 227 commits, 16 PRs, and a perfect 7-day streak. TL;DR This week was a massive exercise in context switching, but in the best way possible. I logged 227 commits across a dozen repos, ranging from low-level p2p networking fixes in Python to aesthetic TUI refinements in TypeScript. The highlights?
Gravy Theory: three chickens, one base
This is a submission for Frontend Challenge - Comfort Food Edition Perfect Landing. What I Built Gravy Theory is an interactive field guide to North Indian gravy, built around a single claim: Butter chicken and chicken curry are not different recipes. They are the same onionβtomato masala, stopped at different moments and finished in different directions. Chilli chicken never touches it at all. Recipes give you minutes. Cooks give you colour.
Dev log #16 Typographic Hierarchy and the Great Obsidian Purge
Spent the week redesigning my portfolio’s blog layout and nuking thousands of stale notes in my Obsidian vault. Between the UI polish and some deep dives into libp2p DHT de-flaking, I pushed 36 commits and managed to delete almost 16,000 lines of clutter. TL;DR I’ve always believed that your digital space needs a good pruning every now and then to stay healthy. This week was the embodiment of that philosophy.
Dev log #15 Refining the Craft: A week of Neovim UI hacking and portfolio architecture
Balanced the scales this week with a near-perfect 1:1 ratio of additions to deletions. Focused on stripping back my Neovim UI and restructuring how I showcase my career history—33 commits and a 5-day streak of pure flow. TL;DR This week was all about the "one for me, one for the world" balance. I spent a significant chunk of time deep in my Neovim configuration, ripping out UI components that didn't spark joy, while simultaneously overhauling my portfolio's experience section.
Dev log #14 Hardening the DHT against Eclipse attacks and the endless battle with flaky p2p tests
Dived deep into libp2p security this week with a new IP subnet diversity feature for the Kad-DHT, while fighting a few stubborn race conditions in the test suite. 3 PRs open and some automated maintenance on my Neovim setup kept the gears turning. TL;DR Security hardening took center stage this week as I focused on making our Kademlia DHT implementation more resilient against Eclipse attacks.
Dev log #13 Hardening Kademlia: A week of p2p security architecture and Neovim maintenance
Spent the week laying the groundwork for major p2p security upgrades while keeping my dev environment sharp. 9 commits and a 7-day streak, but the real work was in the three security-focused issues and a deep-dive discussion on DHT hardening. TL;DR Sometimes the most productive weeks are the ones where you don't actually merge a single PR. This week was all about the long game—specifically, hardening the Kademlia DHT in py-libp2p against eclipse attacks.
Dev log #12 Hardening WebRTC and Polishing the UI: A Week of Networking and Refinement
Spent the week balancing deep p2p networking work in Python with some much-needed UI polish on my personal site. 11 commits and 6 PRs later, I hit a perfect 7-day streak and made the codebase a bit more secure. TL;DR This week was all about the "invisible" work that makes software feel solid. I spent a good chunk of time in the weeds of p2p networking, specifically hardening WebRTC implementations, while also carving out time to refine the typography and feel of my personal portfolio.
Adding WebRTC to py-libp2p: Two Runtimes, Three Specs, and One Unforgiving Private Slot
TL;DR — py-libp2p PR #1309 adds an experimental WebRTC transport (/webrtc-direct and /webrtc) as a v1 node-to-node foundation. It's ~6,700 lines across 41 files, gated by libp2p[webrtc] + enable_webrtc, and merged after four rounds of maintainer review. This is the story of what's inside, why the seams are where they are, and the three bugs that would have shipped silently if the loopback test hadn't been written.
Hardening Kademlia DHT: The Eclipse Attack That Record Signing Doesn't Stop
A few days ago I published Dev Log #9, which covered a security fix I landed in py-libp2p: binding a signed PeerRecord to its signer's identity so an attacker can't relay another peer's record as their own. Then this comment came in from Valentyn Kit, a systems engineer: "Binding the record to its signer kills the forged-record path, nice.
Shipping Docs, Rust Tooling, and a Week of Deep Reviews
14 commits, 2 PRs, 1 issue, and 5 reviews across 3 repos. This week was all about hardening my Rust CLI 'trx' with mdBook and format checks, while doing some heavy lifting on Python backend reviews for the community. TL;DR It’s been a solid, high-energy week. I managed to hit a 7-day commit streak, which always feels great when the flow state actually sticks. The stats tell a story of expansion: 14 commits, 2 merged PRs, and 5 deep-dive reviews.
Dev log #6 Networking Deep Dives and Scaling Docs: My 30k Line Week in OSS
16 commits, 13 PRs, 4 issues, and 13 reviews across 7 repos. This week was a massive balancing act between deep p2p networking fixes in Python, scaling documentation with mdBook, and a heavy rotation of SRE code reviews. TL;DR It’s been one of those weeks where the line count looks absolutely ridiculous on paper—nearly 30,000 additions—but the reality was a mix of high-level architectural setup and low-level bug hunting.
Dev log #10 Kanagawa Dreams and Test Suites: A Week of Refactoring my Neovim and Hardening the Backend
Hit a perfect 7-day streak this week, splitting my time between a massive aesthetic pivot in my Neovim config and a relentless testing marathon for openslate. With 22 commits and 10 PRs, I managed to delete over 2,000 lines of code while shipping a more stable integration layer. TL;DR There is something deeply satisfying about a week that ends with a net-positive refactor and a perfect 7-day streak.
Dev log #10 The Power of the Zero-Commit Week: Stepping Back to Move Faster
A rare week of total radio silence on GitHub—no commits, no PRs, and zero green squares. Sometimes the best thing for a codebase is for the developer to step away from the keyboard and focus on the bigger picture. TL;DR If you looked at my GitHub contribution graph for this past week, you’d see a whole lot of nothing. Zero commits, zero pull requests, and a broken streak.
Dev log #9 Hardening Kademlia DHT and automating the Neovim grind
Seven days of flow. Fixed a peer identity binding issue in py-libp2p, automated my Neovim lockfile merges, and added a massive batch of notes on xv6 and Category Theory. 10 commits and a solid PR in the works. TL;DR I managed to hit a perfect seven-day streak this week, balancing some deep-dive p2p networking work with necessary maintenance on my local environment. The highlight was opening a PR in py-libp2p to tighten up how PeerRecords are handled in the Kademlia DHT.
Dev log #8 Hardening the Orchestrator: A Week of Making dev-publish Resilient
Spent the week deep-diving into my dev-publish tool, focusing on durability and orchestrator resilience. 21 commits across two repos, with a massive cleanup of the publishing logic and some much-needed architecture documentation. TL;DR There is a specific kind of satisfaction that comes from taking a tool you use every day and finally giving it the "production-grade" treatment it deserves. This week was exactly that.
Dev log #7 Reviving DevNotion: 10,000 Lines, Multi-LLM Support, and the Road to v2.1
Spent the week breathing new life into DevNotion—59 commits and over 10,000 lines of code later, v2.1 is officially alive. It was a massive push toward multi-LLM support and public-facing dashboards, keeping a steady 6-day streak in the process. TL;DR I spent the week breathing new life into DevNotion—59 commits and over 10,000 lines of code later, v2.1 is officially alive. It was a massive push toward multi-LLM support and public-facing dashboards, keeping a steady 6-day streak in the process.
I Revived DevNotion (multi agent blog workflow) — And Finally Perfected it
This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built Every Monday standup, someone asks: "What'd you ship last week?" And every Monday I freeze. Did I merge that PR Tuesday or Wednesday? Was the gnarly part in the harvest code or the publisher? I'd sit there scrolling my own commit history like it belonged to a stranger. So back in March I built something to answer the question for me.
Polishing the Rust CLI and Planning the Long Game
39 commits, 11 PRs, and 50 issues across 5 repos. This week was all about making trx feel like a first-class tool and dumping my entire brain into the issue tracker to map out the future. Hit a perfect 7-day streak, too. TL;DR It’s been one of those weeks where the code just flows.
From Rust CLI bug-hunting to a massive Portfolio overhaul
23 commits, 3 PRs, and a 7-day streak. This week was a balance of deep-diving into Rust CLI logic, refining my Neovim setup, and a massive +4,500 line overhaul of my portfolio. TL;DR It’s been a while since I’ve had a "perfect week," but I finally hit that 7-day commit streak. 23 commits, 3 PRs, and 1 closed issue across 4 different repos—this week was the definition of a polyglot grind.
I built a local document Q&A tool around Gemma 4 E4B's 128K context — five days, no RAG, no cloud
Five days, an 8 GB laptop GPU, and a stubborn belief that for the kind of documents I actually read — research papers, internal memos, the API docs of one project — RAG is over-engineering. DeepRead loads PDFs into Gemma 4 E4B's 128K context as page images and answers questions with footnote citations pointing to the exact page. No vector DB. No chunker. No retriever. ~500 lines of Python. This is my submission for the Build with Gemma 4 prompt. The full repo is at github.com/yashksaini-coder/DeepRead.
I stress-tested Gemma 4 E4B's 128K context on a laptop GPU — recall is great, prefill is not
Thursday night I let a benchmark run while I slept. By Friday morning Gemma 4 E4B had answered fifteen needle-in-a-haystack questions across four context sizes on my RTX 5050 laptop. The recall numbers were better than I expected. The latency numbers were worse. Here's both, with the ~30 lines of Python to reproduce it on your own hardware. I keep seeing "Gemma 4 E4B has a 128K context window" repeated as if it were a single property, like "the engine is 3.5 litres". It is not a single property.
Dev Log #5 Building a Claude-style SRE terminal and tackling WebRTC
11 commits, 5 PRs, 1 issue, and 3 reviews across 4 repos. This week was all about infrastructure—from RabbitMQ RCA tools to massive WebRTC scaffolding in Python. Hit a 7-day streak and pushed over 11k lines of code. TL;DR It’s been one of those weeks where the terminal felt like my natural habitat. I managed to keep the streak alive for seven straight days, which always feels great, but the real win was the sheer volume of infrastructure work I got through.
Dev Log #4 A Week of Deep Integrations
A high-output week with 33 commits and over 3,000 lines of new code. I focused heavily on database RCA integrations for OpenSRE and kept the momentum going with a perfect 7-day streak across TypeScript, Python, and C. TL;DR There’s something about hitting a 7-day streak that just feels right. It’s not about the grind; it’s about that rare alignment where every time I sit down at the keyboard, the path forward is clear.
VarCouch — I Built an AI Therapist for Your Code Variables (They Need It)
This is a submission for the DEV April Fools Challenge What I Built Your variables have been through a lot. The endless renaming. The silent judgment from code reviewers. That one time someone called temp2 a "perfectly fine name." They deserve better. They deserve a couch. VarCouch is the world's first AI-powered therapy platform for emotionally neglected code variables.
Perpetual Engine Series Part 2: Real-Time PnL Calculation 📈
In Part 1, we explored Liquidation Logic—the safety net that prevents exchange insolvency. But for that safety net to work, the engine needs a precise, real-time "heartbeat." That heartbeat is PnL (Profit and Loss). Get this calculation wrong, and traders lose money unfairly. Get it right, and the system stays trustworthy at scale. Here’s how I built a PnL system in Rust that handles thousands of updates per second with zero rounding errors. 1. What is PnL?
Turning Weekly GitHub Activity Into Blog Posts on Notion + DEV.to
This is a submission for the Notion MCP Challenge What I Built Every Monday standup, someone asks: "What did you work on last week?" And every Monday, I stare at my screen trying to remember. Did I merge that PR on Wednesday or Thursday? Was that refactor in the auth module or the pipeline? How many repos did I even touch? I got tired of that blank moment.
Simulating P2P Attacks and Teaching AI to Resume Sessions
TL;DR It’s been one of those weeks where the terminal never really closed. I clocked 78 commits and pushed 4 PRs across 9 different repositories, maintaining a perfect 7-day streak. The bulk of the heavy lifting happened in the P2P space—specifically simulating network attacks—and adding some much-needed session persistence to my AI coding tool, nanocoder.
Beyond the Panic: Hardening the Rust SDK
TL;DR Engineering is often the art of managing the "unhappy path." This week was a testament to that philosophy. With 74 commits, 2 PRs, 3 issues, and 3 reviews across 5 repositories, the focus shifted from building new features to fortifying the foundations. The headline? A concerted effort to purge unwrap() and panic calls from our Rust SDKs in favor of robust, Result-based error handling.
I Built a TUI That Makes Rust Code Inspection Feel Like Magic ✨
This is a submission for the GitHub Copilot CLI Challenge The "Why Did I Build This?" Moment Okay so here's the thing. I was working on this Rust project at 2 AM (as you do), trying to figure out where the hell DeserializeOwned was actually implemented. The codebase had like 50,000 lines, and there were these 17 different impl blocks just... everywhere. Scattered across 8 files like someone playing hide and seek with code. And I'm sitting there thinking about my options: Fire up VSCode?
Kleos CLI: Mindsdb Knowledge Base supercharged
Okh so lets begin with the important context, currently there is constant evolution going on in the world of AI agents, and there is large amount of unstructured raw data which keeps on increasing, developers need to constantly simplify complex data and accelerate AI workflows to manage this whole data, so they seek help from tools and frameworks that can make thier task easy.
How I built a AI Agent server
Hi everyone, hope you are all doing well. Today I am going to share how I built an AI agent server and deployed it as API. I'm pretty sure, many of you know by now, what an AI agent is and how much popular they have become. This is Hack Agno an AI agent which is deployed as an API service. With the integrations and applications being developed, I also wanted to create such an application. The inspiration came from Youtube when I was, searching for resource materials to learn Agents.
Automate Discord Messages
Hi π DEVs, in order to get my perspective and objectives of why I did this project and How I built this weekend project, let me first tell you about myself. yashksaini-coder (πͺππ€πππ€ππππ-ππ πππ£) Β· GitHub Just another lazy DEV, who loves Backend, & hates Frontend.
The Friendly Future: How AI Makes Life Easier and Safer for Everyone
Dear Reader, Hi there! I’m writing this letter to share some fun and simple ideas about how latest technology, especially the AI (Artificial Intelligence) is changing our world in different ways. Imagine having a little helper that’s as clever as your favorite storybook character, always ready to lend a hand and make your day brighter! Think of AI as a smart buddy living inside our computers and gadgets. It’s like a magic crayon that learns how to draw better pictures with every stroke.
BMW India to Raise Prices from January 2025
BUSINESS BMW India announces a 3% price hike effective January 2025, across its model range. Lucknow. BMW India has announced a price increase of up to 3% across its model range, effective from January 1, 2025. The adjustment will apply to locally produced models such as the BMW 2 Series Gran Coupe, 3 Series Long Wheelbase, 5 Series Long Wheelbase, X1, X3, and X7. In addition, the company offers premium imported models like the BMW i7 M70, Z4 M40i, and the hybrid XM.
Maoists Kill Two in Telangana, Accuse of Spying
STATE Two villagers hacked to death by Maoists in Telangana's Mulugu district, citing police informer claims. Hyderabad: Maoist Violence Claims Two Lives in Telangana In a disturbing incident, Maoist insurgents have once again resorted to violence, claiming the lives of two villagers in Telangana's Mulugu district. The victims, identified as Uika Ramesh and Uika Arjun, were accused of being police informers and were brutally murdered with sharp weapons.
ICC Issues Arrest Warrants for Israeli Leaders Over Gaza Conflict
WORLD ICC issues war crimes arrest warrants for Netanyahu, Gallant, and Hamas leader Ibrahim Al-Masri. The Hague: In a landmark move, the International Criminal Court (ICC) has issued arrest warrants for Israeli Prime Minister Benjamin Netanyahu, former Defense Minister Yoav Gallant, and Hamas leader Ibrahim Al-Masri. The charges allege crimes against humanity, including murder, persecution, and using starvation as a weapon of war during the Gaza conflict.
Adani Indicted in US: A Blow to India's Business Titan
BUSINESS Billionaire Gautam Adani faces US charges in a $250M bribery scandal linked to energy contracts. Mumbai: A Dark Cloud Over Adani Empire The US indictment against Gautam Adani marks a significant turning point in the ongoing saga surrounding the Indian business tycoon. The allegations of bribery and fraud, if proven, could have far-reaching consequences for the Adani Group and its numerous ventures.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Yash
Contact Yash, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack