Pranshu Khanna @pran.sh · 27/08/2026are we back chat? someone just launched twitter.now after X dropped the brand. claim is basically: → Twitter is reclaimed → not X → early access → "freedom of speech, not reach" → trust signals no idea if this is real or just an internet moment. 010
Pranshu Khanna @pran.sh · 25/08/2026i made a directory of 96 developer ambassador/champion/campus programs. ♥️ ai, devtools, cloud, OSS, data, frontend, student programs, all in one place. check it out if you write tutorials, build demos, run meetups, contribute, or help devs learn tools. pran.sh/blog/awesom...pran.shAwesome Developer Ambassador ProgramsA curated list of developer ambassador, champion, expert, campus, and community programs for builders who write, speak, teach, organize, and create in public. 000
Pranshu Khanna @pran.sh · 25/08/2026i kept losing track of which companies run developer ambassador programs, so I started a list. 📜 it's grown into 90+ programs - Microsoft, Google, NVIDIA, GitHub, HashiCorp, and more. open source and community-maintained, issues/PRs welcome. ♥️ github.com/pransh15/De...github.comGitHub - pransh15/DeveloperAmbassadorPrograms: A list of Developer Ambassador ProgramsA list of Developer Ambassador Programs. Contribute to pransh15/DeveloperAmbassadorPrograms development by creating an account on GitHub. 000
Pranshu Khanna @pran.sh · 24/08/2026i wrote a little something about adoption stonks for models 📈 also, why highest ai benchmarks are great for investors and headlines but devs don't care. companies are spending on ai, but most of it comes from the cheaper models. give it a read ↓ pran.sh/blog/reliab...pran.shHighest AI benchmarks ≠ adoption stonksAnthropic's most expensive model is stalling at 11% of spend while cheaper models handle the daily workload. The FT piece, and the Hacker News thread under it, say a lot about what developers actually adopt versus what they admire. 000
Pranshu Khanna @pran.sh · 18/08/2026I've got a follow up from yesterday! 💡 I wrote about what sets the bar, and realized that if I have shared the problem, I also have to write about how can these projects show receipts. TL;DR | Nobody trust agents because of launch hype. New post → pran.sh/blog/trust-...pran.shCoding agents need receipts, not fansTeams will not trust coding agents because of launch hype. They will trust them when they can see what the agent handles well, where it fails, and how other engineers use it. 000
Pranshu Khanna @pran.sh · 17/08/2026Yeah, that’s the better framing. Stable per-call pricing is one layer, what we will eventually talk about is cost per successful task. Retries, long contexts, tool calls, failed generations, fallback models, eval overhead, all of that becomes part of the real price. 000
Pranshu Khanna @pran.sh · 17/08/2026because the default competitor is not just another startup -- it’s, “I’ll just ask Claude in my editor.” wrote some thoughts on what I think actually matters for coding agents now: trust, distribution, workflow, narrow wedges, and taste. pran.sh/blog/hn-agentspran.shThe Next Coding Agent Moat Is TrustEvery week there’s another coding agent on Launch HN. The question now isn’t whether they can write code, but whether teams will trust them. 101
Pranshu Khanna @pran.sh · 17/08/2026a lot of them are genuinely impressive. But I don’t think the interesting question is “which one writes code fastest?” that part is getting cheap. the more interesting question is: which ones can earn enough trust that teams actually let them touch real work? 101
Pranshu Khanna @pran.sh · 17/08/2026i’ve been noticing a pattern on Launch HN lately: it’s slowly turning into a coding agent directory. every week there’s another agent that opens PRs, fixes issues, plugs into Linear, runs in the background, or “ships like an engineer.” 101
Pranshu Khanna @pran.sh · 14/08/20263/ Another YC coding agent(bullet) is positioning on speed, not “AI magic.” That’s the devtools market now - faster loops, fewer handoffs, clearer workflow ROI. If your agent pitch can’t explain the workflow win in one sentence, devs will bounce. 030
Pranshu Khanna @pran.sh · 14/08/20262/ AI API pricing is becoming product UX, builders care about cost predictability as much as model quality now. DeepSeek price hike + Gemini moving devs to prepaid both point the same way. 200
Pranshu Khanna @pran.sh · 14/08/2026Conversations from this week 👂 1/ Small-team pain in conversations -- AI speeds up frontend shipping, but creates more tiny UI bugs and designer/dev handoff friction. We're being sold, “AI builds it,” but the opp still lies in tools that keep taste, QA and iteration synced. 110
Pranshu Khanna @pran.sh · 11/08/20264th response saying the same. great time to be a community profesh in US, for sure. does anyone else see it too? 001
Pranshu Khanna @pran.sh · 30/07/2026dev meetups in 2026: hundreds watching a person asking claude to code 000
Pranshu Khanna @pran.sh · 20/07/2026delighted to announce that my monthly ai usage limit on zoom has been reset after using it zero times last month 🎉 000
Pranshu Khanna @pran.sh · 14/07/2026anyone using hermes as their daily driver with local models or claude out there? would love to know more about your setups 000
Pranshu Khanna @pran.sh · 13/07/2026not me vibe-coding a grid only to add the snake game for nostalgia purposes on my website high score: 23 pran.sh/ 000
Pranshu Khanna @pran.sh · 12/07/2026The most valuable insights usually happen somewhere in the middle. Certainly not around an F1 car, it was cool though. 000
Pranshu Khanna @pran.sh · 12/07/2026One audience is thinking about strategy, investment, and transformation. The other is thinking about workflows, APIs, performance, and user experience. Attending both was a good reminder that the tech ecosystem is much bigger than the developer bubble most of us live in. 100
Pranshu Khanna @pran.sh · 12/07/2026You'd walk from a cloud provider booth to a startup founder pitching the future of an entire sector. At WeAreDevs, it was all about building. Editors, frameworks, open-source, developer tools, engineering culture, and the practical realities of shipping software everyday. 140
Pranshu Khanna @pran.sh · 12/07/2026two conferences, two weeks apart. very different audiences. At GITEX Europe, the conversations were about AI infrastructure, enterprise adoption, digital transformation, government initiatives, and where the industry is heading over the next decade. 120
Pranshu Khanna @pran.sh · 27/04/2026Happening tomorrow at Mozilla Berlin! 🚨 🎤 Talk on Firefox Mobile and open source contributions 🗺️ Firefox Roadmap & upcoming features 🤝 Networking 🎟️ Raffle 🗓️ Apr 28 // 18:00 // Schlesisches Tor RSVP now! 👇 www.meetup.com/berlin-mozi... 010
Pranshu Khanna @pran.sh · 25/04/2026MDN's old frontend had: ejected Create React App, a Webpack config nobody wanted to touch, CSS so entangled fixing one component broke others, and dangerouslySetInnerHTML as a core pattern. So the team rebuilt it from scratch. Deep dive worth reading 👀 developer.mozilla.org/en-US/blog/... 010
Pranshu Khanna @pran.sh · 24/04/2026Something exciting is happening in Berlin on Tuesday 👀 We're hosting a community meetup at the Mozilla Office - talks, Q&A, networking, and a raffle with the Firefox iOS Team. 💟 🗓️ April 28 // 18:00-21:00 RSVP 👇 www.meetup.com/berlin-mozi... 000
Pranshu Khanna @pran.sh · 08/04/2026Leo McArdle wrote a fantastic walkthrough of the whole architecture. If you're curious about web components in production, modern build pipelines, or just want to see how a site serving 20M+ visitors rebuilt its frontend, this is worth your time. 110
Pranshu Khanna @pran.sh · 08/04/2026But here's what I love most: we used the web platform to build the site that documents it. Custom elements, Shadow DOM, progressive enhancement. The stuff we write about every day on MDN, we're now building with. 110
Pranshu Khanna @pran.sh · 08/04/2026The result? Dev server starts in 2 seconds. Each page only loads the CSS and JS it actually needs. Web components lazy-load in parallel. And our content authors can now write interactive examples directly in Markdown. 120
Pranshu Khanna @pran.sh · 08/04/2026Here's what we reached for 👇 → Lit and web components for all interactivity → Custom server components for static templating → Rspack instead of Webpack → Declarative Shadow DOM for instant rendering → Baseline to decide which web APIs we can ship with confidence 142
Pranshu Khanna @pran.sh · 08/04/2026Here's the short version: our old frontend was a React SPA that had accumulated years of tech debt. Webpack configs that nobody wanted to touch. CSS that was too entangled to scope properly. A dev server that took 2 minutes to start. So we rewrote it. From scratch. 100
Pranshu Khanna @pran.sh · 08/04/2026We just published a deep dive into how we rebuilt @MozDevNet's entire frontend. And I'm so proud of what the team shipped. ♥️ developer.mozilla.org/en-US/blog/... 130
Pranshu Khanna @pran.sh · 12/03/2026Stumbled on git-pulse's snapshot rankings and had to look up mdn/content. ✨ 4th in new committers per month (49) ✨ 5th in new committer percentage (48%) ✨ 5,009 total contributors For a documentation repo, that's wild. And we are actively growing. git-pulse.github.io/snapshots/ 010
Pranshu Khanna @pran.sh · 11/03/2026Sometimes they just... work together. 🤷♂️ I've been reading a lot more lately. And when something stays with me, I want to pass it along - for the community, for friends. Hope this one's useful for you too. cra.mr/mcp-skills-...cra.mrMCP, Skills, and AgentsIf you're not caught up on the current hypewave, coding agents like Claude Code and Cursor have latched onto skills recently. Like with all of these waves, everyone has immediately proclaimed they solve all problems, and all previous iterations of technology are no longer relevant. That's obviously not true, and I want to talk about my thinking behind them. 000
Pranshu Khanna @pran.sh · 11/03/2026A simple way to put it is, "If skills teach you to cook, MCP provides the instruments that let you do it." What I appreciate most is the pushback on the instinct to declare one approach the winner. Every new thing doesn't have to kill the last thing. 100
Pranshu Khanna @pran.sh · 11/03/2026→ Skills are reusable prompt bundles. Lightweight, loaded on demand. They teach the agent how to do something. → MCP exposes tools - the instruments that let you actually do it. → Sub-agents are isolated workers with their own context. Think map/reduce for AI workflows. 210
Pranshu Khanna @pran.sh · 11/03/2026David Cramer wrote something that clarified a lot of the noise for me around MCP, skills, and agents. The key insight: these aren't competing ideas. They each solve different problems. 100
Pranshu Khanna @pran.sh · 10/03/2026Sadly it's Substack, but here is the link: addyo.substack.com/p/critical-... 000
Pranshu Khanna @pran.sh · 10/03/2026As AI does more of the work, what matters most: Asking better questions. Not just what it returned. But whether you asked the right thing. That skill gets rusty if you stop practicing it. - Addy Osmani on critical thinking in the AI age 110
Pranshu Khanna @pran.sh · 04/03/2026The ecosystem is moving fast. The tooling is getting good. The adoption is real. The security conversation is mostly quiet. That gap is going to matter. And I'd rather we start talking about it before it becomes a problem. What are you seeing? 000
Pranshu Khanna @pran.sh · 04/03/2026But here's the thing that stayed with me the whole evening - everyone in that room is building MCPs. Almost no one is talking about what happens when those MCPs go wrong. Security. Authorization. Blast radius. Audit trails. 100
Pranshu Khanna @pran.sh · 04/03/2026The talks were genuinely good: → Viktor from Superhuman on shifting complexity from probabilistic models into deterministic MCP interfaces → Christophe from Slite on progressive tool calling and disambiguation layers 100