My tweets are notes to my future self, YMMV 👦. Trying for positivity! Building: @unraveldottech Alum: @recursecenter, @helpshift https://xitter.cf/t.co/Y1W3sicRXf

Pune, Maharshtra, India
Joined August 2008
🚀 Announcing mcp-clojure-sdk: A Clojure SDK for Model Context Protocol Servers! I'm excited to open-source our Clojure SDK for building Model Context Protocol (MCP) servers! github.com/unravel-team/mcp-…
1
7
3
35
6,805
Vedang (fosstodon.org/@vedang) retweeted
This is a big myth, AC's ONLY recirculate air, they never bring fresh air! If you sit in an AC room for 3/4 hours you are breathing air with 1500 ppm CO2
Replying to @abhinavguptaIAQ
Wouldnt AC do that? Bring in fresh air?
30
18
9
717
68,098
Vedang (fosstodon.org/@vedang) retweeted
Yesterday, someone posted a task runner claimed to be 39x faster than Turborepo. I got really excited, thinking they found some edge case in Turborepo and that I could make something way faster. I open the benchmark repo, and its just straight up, flat out incorrect. Like, not even sorta useful. Not only was it not measuring the task runner parts of the script, it was overfit to a highly specific, completely unrealistic workload. 💀 The entire project is obviously Opus 5.5 vibe coded and Opus cheated the goal. Easy to miss if you're not experienced in build systems. Forgivable! So, I open a PR to show that the algorithm being used can also make scheduling slower, by any arbitrary factor, with only a tiny adjustment. I chose 100x slower than Turborepo for demonstrative purposes. The author fixed some of the problems but there are still grave issues. They're still comparing on an overfit bench that doesn't hold up when you insert the slightest variable, and *insisting* that its right. It is very obviously incorrect, but oh, well. After revision, Turborepo is only 1.36x slower. Down from 39x, but a more realistic number nonetheless. So I figure: "Great! There must be something I can learn to make Turborepo faster." I go digging, and it turns out the other tool is only faster still because it has correctness bugs. Once they correct those, they'll be roughly on par with Turborepo. On top of that, the numbers they post now report with a mix of "% faster" and "✗ faster", using "% faster" whenever the difference isn't big enough to make their tool look good. 1.36x gets turned into "36%", which looks like more than it is to a casual observer. This is a story of how I thought I was going to speed up Turborepo by 39x, and got nothing out of it. I'm not mad; I'm just disappointed. 😄
11
6
8
314
29,181
Vedang (fosstodon.org/@vedang) retweeted
Folks at Mozilla seem to have caught on and are asking the right questions 🫡 bugzilla.mozilla.org/show_bu…
We are underestimating the bad faith eMudhra possibly operated in. They actively added a step to the key generation process causing this failure but are making it seem like a dumb mistake. Let me explain with diagrams and python snippets 👇
52
341
28
5,040
261,378
Vedang (fosstodon.org/@vedang) retweeted
Since the entire internet cares about critical certificates today, a reminder @UPI_NPCI has been running on an expired cert since Sep 2025. Issued by IDRBT, which is now managing all of *.bank.in.
49
464
29
3,078
143,940
Vedang (fosstodon.org/@vedang) retweeted
I read this and I'm terrified, the situation seems intractable. In the python ecosystem alone every cpython install, venv, UV is at risk. Don't get my started on npm, pnpm, yarn, go, rust. My current 2026 security posture: stay home and only connect to the internet from a trusted ISP. The winter is coming. discuss.python.org/t/informa…
73
374
68
3,282
398,077
Emudhra absolutely needs to be shut down. Some things you do not get to come back from.
I do not mean to sound dramatic but post this emudhra should simply not be allowed to continue as a business. this is the same as if delhivery picked up all your product from ecomms and threw it in trash and delivered an empty box to you every single time.
2
7
394
That emudhra can't even show accountability is further proof that they need to be shut down.
> The revoked intermediates themselves have no customer impact. They never issued a certificate, so no certificate in use anywhere relied on them. This is a listed company whose business is digital signatures, completely missing the point. 🤦‍♂️ Everyone who either had emudhra's certs in their trust store or communicates with such entities who had that, is impacted - not just emudhra "customers". Because many web browsers, operating systems, and cloud provides included these, almost everyone in the world is impacted. Cloudflare explains the seriousness of the problem:
1
55
There is still a huge amount of magic to unlock in harness UX. I don't have the answer, but I hate this distinction between "Chat" , "Task" , "Local Coding Agent" and "Remote Coding Agent". I don't want to think about it, I just want to get shit done.
8
8
534
It's crazy how the auto-mode classifier hasn't made its way into all the harnesses even now
20
Salesperson at Pu Na Gadgil: "मॅडम आमच्या कडे कुबेर योजना आहे! तुम्हाला पैसे गुंतवायचे आहेत का?" My wife: "कोण बनणार कुबेर? तुम्ही का मी?" 😂😂 #Pune
7
201
Like all the Gemini models, Argon too is a "sleeper hit". It's a fantastic model, which is going to fly under the radar because for whatever reason Google isn't cool. Using Gemini models in production has been a nice "secret sauce" for the speed/accuracy/cost/enterprise-data-storage matrix when we talk to customers.
5
5
1
170
27,955
💯 The models almost always over-engineer stuff, and this leads to an unmaintainable mess in the long term. Look at the English that models write. It's a good proxy for the code they write too.
This messes with my mind ALL THE TIME When I do stuff with AI I am an *expert* in (eg coding on my project I know well, or doing research in an area I am very familiar with) I spot problems/errors/the model BS'ing me immediately. No big deal, I have it correct or start again BUT when I'm not an expert in an area, I find that I trust it, and then later learn it does stupid stuff. Like a case when I asked 3x AI models to give feedback on a legal case (that I also paid a lawyer for, but lawyer was slow). All 3x models confidently told me X, lawyer then told me Y, and lawyer was right
5
6
510
(Yes I know about "jagged intelligence". And yes, I am sufficiently AI pilled to see the giant boost in productivity they bring)
1
51
Vedang (fosstodon.org/@vedang) retweeted
Absolutely. Fast forward to 2036/46: New medicines, cheaper energy, homegrown chips, satellites protecting crops and cities, rockets launching them and factories building things we once imported. Quite the grift. Unfortunately, none of the above fits in a delivery bag or arrives in <2 minutes, so its contribution to the economy remains questionable. Ignoring the many drones that’ll enable quicker delivery of medicines et al and transport critical materials etc much quicker since being in the air and not on ground we can’t count its contribution to the economy. Because obviously a country that can’t manufacture its own chips, aircraft engines, or advanced machinery but can deliver imported avocados in a few minutes is clearly winning the economic race.
Replying to @imDhananjay
in a decade we will realize most of the deeptech is a grift and quick services + quick commerce companies are what drives more for the economy
27
88
10
760
20,508
Vedang (fosstodon.org/@vedang) retweeted
SCREAM IT FROM THE ROOFTOPS LORD TORVALDS
22
254
34
2,201
76,869
Of all the clever ideas we're trying to encourage org-level learning, this one is the most fun :) Greybeard: Sending questions to your teammates as a way to review and improve design.
Introducing Greybeard, A lot of folks are building with Claude Code and Codex. But, sometimes they just need an engineering expert to chime in. Mostly because the answers requires more context about their org or it's simply an unknown unknown for them. Let me know if you want to try out Greybeard.
1
1
6
382
For over two months now, I've been locked out from my X account on my laptop and desktop, because of X Bookmarks. X Bookmarks are a black hole. I'm hoarding them all the time and never reading them. I was getting on a long flight and decided to fix this. I fired up an agent, asked it to open my bookmarks one by one, and index it into my note-taking system (Denote in Emacs). Then I relaxed on the flight with my offline copy, following threads and connections to my heart's content. Apparently, X's anti-bot gods were not amused. My mobile session survived, thankfully. But I've been exiled from thoughtful long-form posting and basically reduced to shit-posting and reacting :P. Sorry X gods! All I wanted was to make X more useful for myself. Please accept my humble apology! Can someone please help me get out of this purgatory? Please help me get my account access back!
2
1
406
Vedang (fosstodon.org/@vedang) retweeted
I’m the Corporate Vice President of Global Talent Strategy at Microsoft. People say I hire H-1Bs. My badge says I source world-class talent that can’t leave. That second part? That’s the whole program. Last year we filed 4,812 petitions. 97% got approved. Everyone talks about the lottery like it’s luck. It’s great for us, because it lets us call the outcome chance. It isn’t. The outcome got decided months earlier by a team that writes the specialty-occupation language before the req even opens. They’re fantastic. I’m proud of them. This year Copilot started drafting the language for them. Turns out Copilot is really good at describing a job only 1 person on earth could possibly do, as long as that person is already in our system. We called the workstream PERMANENCE. Legal made us rename it. Now it’s Project Continuity. Same slides. Domestic candidates apply. Plenty of them clear the bar. We go with the H-1B anyway. Why? Because the H-1B already took the band. The band is Level II prevailing wage. Level II is the median we asked for. The people who can quit get paid off a different median, one they talk about openly at lunch. The H-1B negotiates off the LCA. The LCA’s public. Basically nobody reads it. I read it every quarter. Honestly, it’s calming. We track the result as diversity and inclusion. 68% of the engineers who joined Azure last cycle came in on temporary status. The dashboard shows that number in a really nice green. What it doesn’t show is the 28% fully-loaded cost delta. That lives in a different workbook. Finance owns that one. Finance is proud too. Let me tell you about Raj. Raj has been on Azure Storage for 6 years. He knows the codebase better than the guys who wrote it, and 2 of them already left for counteroffers. Last spring his manager, Dana, asked why we couldn’t just promote him to staff and backfill locally. So we set up a talent review. 40 minutes. I asked Dana about pipeline health. Dana asked about the codebase. I asked about competitive intensity. Dana asked about the codebase again. I asked whether she had a growth mindset. She said she thought so. We agreed to take it offline. Offline is where Dana’s req went to die. Raj stayed. Raj always stays. He came in on another company’s visa, and we transferred it. Counsel has a template for that. The new $100,000 fee only hits talent that’s still overseas. Raj was already here. Transfers keep the leverage and skip the toll. Finance made a slide about it. There’s a little rocket on it. The transfer is the point. Look, if you can quit on Friday, you’ve got leverage on Thursday. If your legal status ends the day your job does, you’ve got Thursdays and that’s it. We never have to threaten anybody. The statute does that for us. Raj has read the statute. He’s also read his priority date: 2014. Projected to go current in 2031. Between now and then we’ll bump his Level II wage twice, and both bumps will be smaller than what we gave the people who can walk. We call that pay equity, since the formula treats everyone exactly the same. Only some people get to argue with it. His wife’s on an H-4. Back in Pune she was a pharmacist. Here she’s a really organized volunteer. His daughter turns 21 in 2029, which is the year she ages out of his case. She wants to be a doctor. On paper, in 2029, she becomes an international student in the only country she remembers. HR flagged it as a retention risk. Finance flagged it as a retention asset. We went with Finance. Some people call this a caste system. We call it a two-tier compensation architecture, and it’s working exactly the way it’s supposed to. In the workbook, the line is column AF. The header says Mobility Status. There are 2 options: Portable and Anchored. Nobody ever types the word caste. Excel’s never needed it. The Portable folks sit above the line. They get the counteroffers, the refreshers, and the freedom to ignore the 11pm call. When a Portable engineer mentions he’s “exploring options,” a VP takes him to lunch somewhere with no prices on the menu. When an Anchored engineer explores options, he gets 60 days to do it. That’s the grace period after you’re let go. They call it grace. We didn’t name it. We’d have named it better. The Anchored folks sit below the line. They get the scope, the on-call rotation, the “stretch assignment,” and a calibration note that says high potential, visa-dependent. Nobody writes down that second part. Everyone in the room already knows. The room claps for the first part. When a Portable engineer pushes back on a deadline, we call it psychological safety. When an Anchored engineer pushes back, well, he doesn’t. We call that alignment. At the all-hands, both tiers sit together. Same hoodie. The hoodie says One Microsoft. And at the hoodie level, it’s true. During the January layoffs, the Portable folks got severance, a sweet LinkedIn post, and 14 recruiter DMs by lunch. The Anchored folks got severance and a countdown. A guy on Raj’s team spent his last 3 weeks training his replacement and his first 3 weeks unemployed applying to 212 jobs from a Starbucks in Bellevue, because his landlord wanted proof of income. He landed something on day 57. We sent him a survey about his offboarding experience. He gave it 4 out of 5. He said everyone was really kind. And they were! The people were kind. The people just didn’t design the system. Belonging scores go up when the alternative is a one-way flight. Velocity goes up when nobody on the team can say no. Viva pings Raj at 11:40pm to remind him to protect his focus time. He reads it on the incident bridge. His engagement numbers are fantastic. In March his dad died in Hyderabad. Raj didn’t go home. His visa stamp had expired, and the next consulate appointment was 11 months out. If he left, he might not get back in. And getting back in meant the job, the house, his daughter’s school, the 2014 priority date. So he watched the cremation on his phone, propped up against his monitor, between a design review and an on-call handoff. His manager approved 3 days of bereavement leave. He used 1. The other 2 roll over. We’re super flexible about leave. Critics say we’re replacing Americans. Internally we call it workforce durability. Durability just means they stay. Durable talent brings specialized skills. The specialized skills have signed the at-will acknowledgment and the non-compete, and we’ll enforce it if they try to jump before their date’s current. The date’s never current. Everybody knows what happens if we pull a petition. We’ve never had to explain it twice. (Fine, immigration counsel will tell you that after 180 days the priority date survives a withdrawal. We leave that out of the onboarding deck. Onboarding decks should be uplifting.) In March we won Best Employer for Global Talent. The plaque’s in Building 92. Most of the people it honors can’t switch employers to find out if it’s true. Some of us have started thinking of the backlog as infrastructure. We don’t lobby against it. In our policy comments we call it a “stable pipeline environment.” Stability’s one of our values. It’s on a poster, right next to Courage. I meet with the team every Monday. They know the cap. They know the premium processing window. They know which vendors will staff the interview loop so the candidate’s prepped and the manager never gets surprised by an acceptance. They cheer when a req closes under budget and the diversity and inclusion cell turns green. Last quarter it went green in 4 orgs. We sent a note. It said belonging and innovation. Both totally accurate. Raj belongs. We innovated. Dana left in August for a competitor. We matched the offer in a day. She still said no. People who can leave are like that. Raj sent her a goodbye message in Teams. He couldn’t make the drinks. He was on call. I’m so, so proud of this team. They took a regulatory constraint and turned it into permanent leverage. And the leverage compounds. We report it as growth. The analysts love growth. So do I. My equity vests every quarter. Raj’s priority date goes current in 2031. His father’s never will.
257
254
71
1,808
502,711