rambadri (@rambadri) profile picture

Co Founder of KarmYog Education Network Pvt Ltd and Founder GlobalTHEN

Joined December 2007
Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)Photo by rambadri (@rambadri)
rambadri retweeted
The traditional lighting of the lamp marks an auspicious beginning to Bengaluru Tech Summit 2026, setting the stage for three days of innovation, collaboration and technological advancements. #BengaluruTechSummit #KarnatakaInnovates
2
4
5
392
rambadri retweeted
Have you ever wondered why catching Starship is so much harder than catching Super Heavy, even though they both return to the same launch tower? 🔥 💡 The answer comes down to four major engineering challenges that make Starship’s recovery fundamentally different 👇 ⚡ The first problem is shedding an enormous amount of energy At hot staging, Super Heavy was traveling at roughly 5,800 km/h (3,600 mph). Starship, meanwhile, had to return from orbital speeds of roughly 27,500 km/h (17,100 mph). That’s nearly five times faster. Because kinetic energy increases with the square of velocity, each kilogram of Starship at orbital speed carries roughly 22 times the kinetic energy of a kilogram of Super Heavy at separation. That works out to nearly 30 million joules per kilogram. Almost all of that energy has to be dissipated before Starship can safely reach the tower. One option would be to use rocket propulsion to cancel out its orbital velocity. However, scrubbing off roughly 7.7 km/s of speed using Raptor engines alone would require a massive amount of propellant. The rocket equation makes this approach especially punishing. Every extra kilogram of landing propellant has to be hauled into orbit first, dramatically increasing the fuel needed at liftoff. Instead, SpaceX uses Earth’s atmosphere to bleed off almost all of Starship’s orbital velocity. That saves an extraordinary amount of propellant, though it introduces another major hurdle. 🔥 Surviving extreme atmospheric heating comes next As Starship plunges into the atmosphere at hypersonic speeds, powerful shock waves compress and heat the surrounding air to blistering temperatures. Thousands of ceramic heat-shield tiles protect its stainless-steel structure from the intense heat. Simply keeping those tiles attached isn’t enough, though. Superheated gas can seep into the gaps between them, risking damage to the underlying structure. For Flight 15, SpaceX carried forward upgrades from Flight 14, including extra tile-retention hardware in vulnerable areas and redesigned curved tiles that reduce heating between adjacent tiles. Because Super Heavy never reaches orbital velocity, its return doesn’t expose it to anything close to the same thermal stress. And there’s another complication. A heat shield that survives one reentry isn’t necessarily ready to fly again. Starship’s thermal protection system must eventually withstand repeated missions without major repairs or refurbishment. That’s critical, since rapid reusability is one of the core reasons SpaceX designed Starship to be caught rather than discarded. Yet surviving reentry still isn’t enough. Starship also has to arrive at the exact right spot. 🎯 Hitting a precise target from orbit raises the stakes even further About 56 minutes before the catch, a single Raptor engine fired for just 10 seconds to initiate Starship’s return. That brief deorbit burn wasn’t meant to eliminate orbital velocity. Instead, it nudged the spacecraft’s trajectory so atmospheric drag could take over the much larger job of slowing it down. Starship then entered the upper atmosphere thousands of kilometers away over the Pacific Ocean. From there, its four aerodynamic flaps controlled its orientation and fine-tuned the forces acting on the vehicle. Super Heavy uses grid fins to steer during its return, but Starship’s flaps have to handle a far wider range of flight conditions. As Starship decelerates from hypersonic through supersonic and down to subsonic speeds, its guidance system continuously adjusts its attitude and flight path. The challenge is maintaining the right balance of altitude, speed, and trajectory while aerodynamic forces shift dramatically throughout reentry. For Flight 15, the return corridor crossed sparsely populated parts of northern Mexico and South Texas. Starship maneuvered around major population centers in the Rio Grande Valley, passed north of South Padre Island, headed offshore over the Gulf of Mexico, and made its final turn toward Pad 2 at Starbase. Think about the guidance precision required. A spacecraft returning from orbit must dissipate nearly all of its immense kinetic energy while threading a carefully controlled trajectory straight back to a single launch tower. It also has to arrive at a low enough speed, in the proper orientation, and with enough propellant remaining to pull off the final maneuver. That brings us to the most visually spectacular part of the entire recovery. 🚀 Executing the landing flip with pinpoint precision is the final test Super Heavy approaches the launch tower already vertical, using its grid fins and Raptor engines to guide its final descent. Starship comes in belly-first. It has to rapidly swing its massive frame upright, stabilize its attitude, and align itself precisely between the tower’s mechanical arms. SpaceX’s official Flight 15 timeline allotted just 18 seconds between the start of Starship’s landing burn and the catch. During those 18 seconds, three sea-level Raptor engines ignite to kick off the maneuver. The spacecraft rotates upright while its flight computers constantly regulate engine thrust and vehicle attitude. The engines then step down from three to two, giving the vehicle finer control as it nears the chopsticks. Finally, it transitions to a single engine for the last moments of descent before shutting down as the tower takes its weight. Consider the coordination involved. The guidance system must balance translation, rotation, thrust, and descent rate while positioning a massive spacecraft within a narrow capture envelope. Unlike a conventional vertical rocket landing, Starship must first transition from an aerodynamically controlled, belly-first glide to an engine-powered vertical approach. All of this unfolds within seconds, right after the vehicle has completed one of the most punishing atmospheric reentries ever attempted by a reusable spacecraft. 🧠 What makes SpaceX’s approach so ingenious is how seamlessly the entire recovery system works together Trying to solve every phase of the return with rocket propulsion would carry a crushing propellant penalty. Instead, SpaceX delegates the toughest parts of the recovery to systems purpose-built to handle them. The atmosphere dissipates most of the orbital kinetic energy without consuming onboard propellant. The heat shield protects Starship from the intense thermal loads of that deceleration. The four aerodynamic flaps provide the control authority needed to manage its attitude, energy, and trajectory throughout atmospheric flight. And the Raptor engines take over once aerodynamic control alone can no longer deliver the precision needed for the final catch. That division of labor allows SpaceX to recover an orbital spacecraft without carrying enough fuel for an all-propulsive return. Yet the engineering trade-off goes deeper than saving propellant. SpaceX is shifting much of the cost of returning from orbit away from expendable propellant and toward reusable hardware built to endure extreme thermal and mechanical stress. The potential economic payoff is enormous. Cutting back on the propellant reserved for recovery frees up more of Starship’s mass capacity for useful payload. However, that advantage only becomes truly meaningful if the heat shield, flaps, engines, and other systems can survive repeated flights without extensive refurbishment. That’s why catching Ship 42 is such a landmark milestone. SpaceX has proven that its thermal protection, aerodynamic controls, propulsion, and guidance systems can work in concert to recover an orbital upper stage right at the launch site. The next engineering hurdle is proving that the same spacecraft can do it repeatedly. If SpaceX can bring Starship home, inspect it, refuel it, and launch it again without rebuilding major systems, the economics of getting payload to orbit could change dramatically. That first catch proves the recovery architecture works. Repeated reflights will determine just how much of its economic potential SpaceX can unlock.
196
934
178
5,998
803,476
rambadri retweeted
we spend ₹10-15 lakh a month on ai subscriptions running a film studio out of bhopal, and our usage is huge it's very different from bombay or bangalore, because a lot of the people we work with aren't native english speakers or don't come from privileged backgrounds, they're just here to work, so we teach them from the ground up, the tools, filmmaking and sometimes even the language that's where most of the money goes, @higgsfield_ai and @HeyGen for the video, @claudeai and chatgpt for the thinking and writing, @WillowVoiceAI and @WisprFlow so people can just talk instead of type, and @heyclicky has helped a lot too the way we teach is seniors sit with them but let them make their own mistakes, and explain what went wrong afterwards, and we let them burn credits while they learn they don't touch client episodes, they make episodes for our own social channels, so the mistakes cost us credits and not a client managing a big team got a lot easier because of these tools, and most of our work is ai assisted now and it works well and we use grok bot to figure out where we're wasting higgsfield credits and other resources, because at this spend the waste adds up fast
37
15
3
342
26,091
rambadri retweeted
"I Teach at a Business School, It's Time to Shut Them Down" says Prof Chris Marquis from the University of Cambridge Judge Business School. I agree entirely and have been saying this for 2 decades. India would do well to close down business schools and focus on startup incubators. We need large scale startup formation and a lot of experimentation.
163
509
46
2,530
132,921
rambadri retweeted
The attention economy is wild! Last week, waiting to board my flight to delhi, I see commotion around a gentleman. The kind of commotion you see around government officials - laced with servitude and respect that comes from tenure and not necessarily impact. My curiosity gets the better of me. I want to know who he has. As he boards the flight, I happen to catch his name on the boarding pass. As I board, the flight attendant recognizes me. His KPI includes a namaste to everyone. But the enthusiastic smile and child like excitement is reserved specially for me. The gentleman is already seated. No one knows him on this craft. His crowd has already left him. He is a commoner now. I take a seat. The first thing I do is google the gentlemen’s name. Almost convinced of his role, I add IAS to the search. His name and picture pops. IIT Kanpur computer science Masters in public policy from Princeton PhD in economics from Princeton 1991 batch of IAS Currently a secretary FML! The article heralded him as “The Intellectual Powerhouse and Fiscal Architect of Modern India” And here was I - a complete non-entity - bring drooled at by passerbys. “Big fan sir” “Love your content” No bro. We all got to love HIS content. Applaud him. Celebrate such individuals. Recognize then. I would love to start a series on such personalities, that remain behind the scenes, quietly changing the way we live and experience our lives. The attention economy feels so twisted.
32
9
2
429
82,302
At this year’s @litlivemumbai , I shall be in conversation with Naresh Fernandes, the brilliant editor of @scroll_in . The session is titled “Gandhi Matters”, and will be held at the NCPA’s Experimental Theatre, 24th October, 630 pm onwards. @tajmahalfoxtrot
13
16
1
66
14,190
Visited Captain Bheri during Durga Puja to offer prayers and experience the festive spirit. May Maa Durga’s blessings bring happiness, peace and prosperity to everyone.
2
4
12
341
ज़ब कोई ईमानदार पत्रकार न्यूज चैनल छोड़ कर अपना स्वतंत्र यूट्यूब चैनल बनाता है तो उसकी पत्रकारिता देखने लायक होती है ये जिगरा गोदी मिडिया मे नहीं है सांकेत उपाध्याय ने पूरी पोल खोल दी चुनाव आयोग की..
157
5,571
80
15,549
177,657
Can you imagine a 2-hour conversation between a VC and an AI researcher on AI and LLMs entirely in Sanskrit? We just recorded one. Could this be the world's first technical podcast in Sanskrit? Can't wait to share it. Here is a raw glimpse
326
1,039
245
5,778
674,662
rambadri retweeted
ElevenLabs is officially on OpenRouter. You can now call 9 Text to Speech models, with up to 90+ languages, and 2 Speech to Text models with speaker labels and word-level timestamps. All @ElevenLabs models are 50% off, only on OpenRouter, through October 19, 8am PT.
30
35
15
500
47,738
We are making Markdown files work natively across Google Drive and Docs. You can now preview .md files in Drive, open them in Docs, edit them, comment on them, and collaborate without converting the file into a Google Doc!
937
1,342
952
21,021
1,446,654
rambadri retweeted
install it and give me feedback with: claude plugin marketplace add anthropics/claude-plugins-community claude plugin install html-plan@claude-community here's an example: claude.ai/artifact/CUF7bzFny…
24
29
4
631
61,462
rambadri retweeted
This is f*cking insane. This Claude Code tip saved me thousands of dollars. once Opus 5.5 is your main model, stop burning it on work Sonnet 5.5 can do, while Fable 5.1 sits idle hand the grunt work to Sonnet 5.5 subagents and put Fable 5.1 on call run /advisor fable Opus 5.5 plans and ships the final code Sonnet 5.5 subagents read, edit and run the tests Fable 5.1 reads the full session, every tool call included, and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Sonnet 5.5 builds. Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split anyone still running one model for everything is paying Opus prices to decide whether a file exists - the full tree > Opus 5.5 on high runs the main session > explorer reads the code on Sonnet 5.5 > worker edits and runs tests on Sonnet 5.5 > researcher pulls the docs on Sonnet 5.5 > all three on medium > Fable 5.1 on call for main and every subagent paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: sonnet, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳ code.claude.com/docs/en/advi…
21
22
299
49,264
rambadri retweeted
Absolutely recommend using Cache Control in Claude Code Probably one of the Mods that will save you the most tokens and help keep your sessions going much longer It adds this bar for Claude’s 5 minute cache and sends notifications to help keep the cache warm Install command: npx claude-code-templates@latest --mod observability/prompt-cache-control
117
99
21
2,769
235,839
rambadri retweeted
We're adding a new plugin to Claude Code: You should Know. It scans Claude's output for important information you might miss to help keep you in the loop. Enable it with: /plugin enable cc-plugin-you-should-know@builtin
385
937
234
16,110
1,720,584
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks: Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better: Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better: Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better: Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work! In summary: - As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding. - Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
1,711
6,767
1,582
56,855
8,231,063
rambadri retweeted
Every time you let Opus 5.5 run a long task on its own, have it vibe-code a quick 𝗛𝗧𝗠𝗟 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 like this first. Then give it 𝗮 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁 𝘁𝗵𝗮𝘁 𝗼𝗻𝗹𝘆 𝗯𝘂𝗶𝗹𝗱𝘀 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱𝘀: → Name it dashboard-builder, set its effort to medium, and preload a design skill → The first time, it asks what style you like and saves it to memory. After that, every dashboard fits your taste and the task at hand → Call it before every long task. It builds the dashboard in the background in about two minutes, and the main session keeps coding on high without stopping → The dashboard shows four things: task progress, what's stuck, questions waiting on you, and what it'll do by default if you don't answer Send this prompt to Claude Code 👇 "Set up a subagent that only builds progress dashboards: 1. Create dashboard-builder in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). It can only read and write the .dashboard/ folder and its own memory. 2. The first time, it asks me what style I like: dark or light, dense or airy, and one accent color. It saves my answer to memory and follows it every time. Pick the panels for the current task; don't use a template. 3. The dashboard is one HTML file showing tasks and their status, questions waiting for me with the default action, the latest deliverables, and anything stuck. Use the real clock for every time. It opens with a double-click and refreshes itself every 10 seconds. 4. Add a rule to ~/.claude/CLAUDE.md: for any task with more than 5 steps or that should take longer than 30 minutes, have dashboard-builder set up the dashboard before starting; update it after every step; when you need a decision from me, add it to the questions list and keep going with the default. Show me the contents of the files you'll create or change, then explain the whole flow in words a 10-year-old could follow. Don't write anything until I confirm."
157
211
31
3,862
333,091
microsoft quietly open-sourced one of the best ai data analysis tools out there. it's called data-formulator. connect any source, csv, postgres, bigquery, even a live url, then build charts with a mix of drag-and-drop and plain english. the ai agent writes the sql and transforms underneath and hands back a chart you can actually edit, not a code dump. > drag fields onto x/y/color and it builds the chart > anchor a cleaned result so follow-ups don't drift back > branch any chart to explore a variation > connect live data with auto-refresh bring your own model key and run it locally.
11
107
1
576
32,993
क़िस्सा गांधी के टूटे दाँत का यह गांधी गाथा का एपिसोड 5 है। पूरा एपिसोड आप Awadh Punch और DoubleCheck के YouTube चैनल पर देख सकते हैं - youtu.be/-0hkhU42YFc?si=MOXH… #mahatmagandhi #gandhigaatha #gandhijayanti #history #redfort
6
1
24
1,351
Today we announce our new unified multi-agent framework that provides creators with a system for generating temporally consistent, long-form video narratives while mitigating visual drift and pipeline error propagation. Learn more: goo.gle/4yVih5m
58
270
24
2,212
126,055