PhD, @MIT. BTech, @iitmadras. AI, ML, Climate, Upskilling, Education. Views are my own.
Bengaluru, India
Joined September 2009
- Tweets3.4K
- Following789
- Followers3.1K
- Likes5.1K
Deepak Subramani retweeted
Annachi takes on AI coding 🥲 No AI coding took on Annachi 😂 Catch Retired NOT Hurt in Chennai on Nov 21 and Bengaluru on Dec 5 - the last two shows of 2026.
Vaanga Makkale! ❤️ 🇺🇸 🇨🇦 🇦🇺 Coming soon 🙌🤗
Deepak Subramani retweeted
Yup, it's the new form of performative busywork.
Deepak Subramani retweeted
I think voter apathy or long weekend is a very small problem compared to the data errors that have a very high probability and plausibility. The attack on hard-working tech bros who may have taken off to a resort after voting at 7 am is uncalled for.
Deepak Subramani retweeted
Everyone wants to have solved a hard problem, but almost nobody wants to live inside the grind of actually solving it. The breakthroughs belong to the few who are obsessed with the process, not just the idea of the outcome
Deepak Subramani retweeted
Finally! This might be the end of Leetcode interviews
Code comprehension is still important, especially in the (early) age of agentic coding
Goodbye to LeetCode? Google just updated its interview process. AI is now a part of it.
They have introduced a new round called Code Comprehension.
The idea behind this round is to drop the candidates into a 200-500-line codebase with Gemini available for use.
This round evaluates:
- Can you read someone else's code
- Are you able to debug independently before utilizing AI
- Can you catch when Gemini is wrong
Deepak Subramani retweeted
Claude Managed Agents dynamic workflows are now available in public beta. It's a new type of multiagent orchestration, built for your most ambitious workloads.
A lead agent writes a plan that runs across many agents in phases, combining the results at the end.
Deepak Subramani retweeted
the most common failure case I see is when people are working outside their domain of expertise and don't know how to be precise with their prompts and plans, so they have to spend a lot of turns iterating imprecisely
Deepak Subramani retweeted
I am surprised that people are surprised this is how I prompt Claude.
Talk to Claude the way you would a coworker. There's no secret to prompting. There's no need to be overly scaffolded or prescriptive for most tasks -- give Claude a goal, and it will figure it out.
Back in the Sonnet 3.5 days, your prompt mattered a lot. Nowadays, it's much more important to communicate to the model:
1. What you want it to do
2. How much effort you want it to spend
3. How it should verify that it did the right thing
Deepak Subramani retweeted
"explain how Shazam works"
I had no idea
Karpathy is so right about this
custom explainer videos will change education
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.
Deepak Subramani retweeted
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.
Deepak Subramani retweeted
Because so much of the debate about AI and jobs is driven by fears of outright replacement, there's a much more likely way in which AI could make work worse that isn't getting much attention. Here's my case:
1) A growing share of knowledge workers are managers of AI agents rather than doing the work themselves.
2) Being a manager (of humans) actually kinda sucks. You don't get to practice the craft you trained for; being responsible for others' mistakes is super stressful; and your attention gets split between dozens of things.
3) But we managers don't get to complain — it's higher pay and higher status, and mentoring people and watching them succeed is incredibly gratifying. We chose to get promoted.
4) Being a manager of AI brings all of the negatives without any of the positives. When everyone is a manager, it's not high pay / high status. And the role change is forced upon you.
What am I missing?
Deepak Subramani retweeted
Periodic reminder: professors are terrible at forecasting the future. If they were any good at it, they wouldn’t be professors: they’d be making millions in the stock market.
Deepak Subramani retweeted
We instituted an official AI Writing Policy at @Clay.
Massive thanks to @sophiebits on our engineering team who wrote this.
Originally this was just for eng, but other teams found it so helpful we expanded it company-wide.
Here are the four guiding principles:
1. You must stand behind every idea and sentence
It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it.
2. Writing is thinking
Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter.
3. More time should be spent writing a document than consuming it
If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to.
4. Longer is not better
AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt.
You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
Deepak Subramani retweeted
when a lot of trash gets funded, people get the idea that they can send in their trash and get it funded too.
Deepak Subramani retweeted
it's basically impossible for someone to just "show you their prompt" now, because everything is about references, skills and examples
I often ask my agent to look at 3 other repos I've made first, search the web for references, use other AI APIs, etc.
Deepak Subramani retweeted
SIP investors when they realize their returns are lower than Fixed Deposits, plus they have to pay 12.5%-20% in taxes to the Finance Ministry.
xitter.gq/be_mewadi/status/21042…
