Abhijeet Dipke's real agenda finally came out 🚨
Question - Now that the protest is over, why don't you raise questions against reservation as many students are asking for it?
Abhijeet - That's not my headache. Now the government should deal with all it's issues
Reporter - If that's not your headache, then how was this NEET protest your headache? Students are the one suffering in both cases
Abhijeet - I don't think population based reservation is anything wrong. It should be there. If SCs are 15% of the population, they should get 15% reservation
Reporter - Then why not apply the same logic to paying taxes? If SCs are 15% of the population, should they also pay 15% of the total tax? Why should the general category pay all the tax? Shouldn't everyone contribute according to the same population logic? Would that be fair?
Abhijeet just made the same sad face he keeps making after losing every debate. Give her a raise man 🙏
Belly fat doesn't start with your diet.
It starts with cortisol cementing fat around your organs, a body locked in famine mode, and a nervous system stuck in survival mode.
Here are 7 science-backed ways to burn it for good:
1. No food 3 hours before bed.
Monday morning questions for you:
Which activities, if doubled, would make your life meaningfully better?
Which activities, if halved, would make your life meaningfully better?
.@mosseri: "My experience is that the strongest product leaders are less visionaries and more curators. They curate teams and ideas, and many of their greatest success stories are often ideas from other people."
Learn to love the interruptions. Find the fun in the delay, the humor in the challenge, the pleasure in the daily commute.
A great deal of life is spent dealing with interruptions and waiting for the conditions to turn. We think, "If I can just get past this, then things will open up." But the interruption is not standing between you and your life. It is your life.
Yes, I prefer hassle-free days too. But you'll rarely find a situation that is all bad. There are little pockets of joy folded inside the annoyances we face. There is always fun to be had, if you go looking for it.
This is one of the arts of living. It's the art of enjoying the imperfect days. It's the art of making all the moments count.
Richard Feynman, Nobel de Física, lo dejó claro:
"La mayoría de personas saben muchas cosas. Pero no saben pensar."
Dio esta clase de 1 hora sobre física e imaginación.
Sus 12 lecciones de vida:
1. La imaginación le gana al conocimiento.
Great post on how to think about open source AI and the applied AI layer. Two things will always be true in AI. Frontier intelligence will likely remain at the forefront of solving brand new used cases and often be used for orchestrating and planning of any type of complex workflow.
At the same time, as use-cases become mature and predictable in an enterprise context, you can begin to peel off some set of the tokens to either lower cost open or closed models *or* models that are trained for the task at hand.
Doing this too early in the adoption curve of any new use-case doesn’t make sense as you don’t know what you’re optimizing for, which is why there will always be a bit of a lag here.
This process can essentially run on forever as there is no end for both the benefits of frontier intelligence or tuned models. This is why the spend and token volume for both approaches will continue to go up for years to come as we’re still early on both.
Again, the only reason this dynamic is possible though is because of the applied AI layer that can effectively eval their workflows in a specific domain, choose a mixture of models to solve tasks, and have enough scale to eventually train their own models for their purposes.
PRODUCTSPEC: OPEN STANDARD FOR SOFTWARE INTENT
tl;dr ProductSpec is the open standard for software intent before implementation.
The more I worked on PRDs, the more obvious one thing became: Product specs need an open standard.
Why?
Because the PRD has become an overloaded artifact.
Every company has its own template. Every team has its own preferred format. Every PM has their own way of writing. That was manageable when the only readers were humans sitting in the same org context.
AI changes the requirement.
A Product Spec now has to be readable by humans and executable by AI agents.
That means the spec has to carry intent clearly enough for a designer, engineer, product leader, and coding agent to understand the same thing:
• What problem are we solving?
• What is the product bet?
• What is in scope?
• What must be true before this ships?
• What metrics tell us whether the bet worked?
This is why I open-sourced ProductSpec.
ProductSpec is a Markdown standard for software intent before implementation.
The core sections are simple:
• Problem
• Hypothesis
• Scope
• User Experience
• Acceptance Criteria
• Success Metrics
The deeper design principle: Structure the parts machines must execute or compare. Leave readable the parts humans must reason about.
That is why ProductSpec keeps Problem and Hypothesis as readable prose, while giving structured formats to the parts agents and tools need to parse:
• Scope: what is in, out, and deliberately cut
• Acceptance Criteria: what must pass before launch
• AI Evals (within Acceptance Criteria): the evals an AI feature must pass before shipping
• Success Metrics: what should be measured after launch
When to use ProductSpec
ProductSpec is not for every act of building. It is for consequential software work where intent needs to survive handoff. For an individual builder, a Product Spec is useful when the work is complex, risky, long-lived, or being handed to an AI agent loop. For quick experiments, one-off scripts, or throwaway prototypes, it may be faster to brainstorm, build, and iterate directly.
For a team or organization, ProductSpec is most useful when coordination cost appears: multiple people, multiple agents, design and engineering handoffs, customer-facing launches, AI features with evals, or decisions that will need to be revisited later.
ProductSpec does not replace Git, Jira, Linear, Figma, analytics tools, OpenSpec, Spec Kit, or AI coding agents. It sits upstream of them.
ProductSpec -> Engineering Spec -> Tasks -> Code -> Evaluation -> Learning
-- Git stores implementation history. A Product Spec can live beside code in Git, but code commits should not be the first durable record of why the work exists.
-- Jira and Linear store work history. A Product Spec can become epics, tickets, or tasks, but it should remain the durable statement of intent behind those tasks.
-- Figma stores design artifacts. A Product Spec can link to prototypes, mockups, or screenshots through user_experience, but it does not replace the design source of truth.
-- Analytics tools store outcome data.
-- OpenSpec and Spec Kit turn intent into engineering plans.
-- AI coding agents execute implementation tasks.
-- ProductSpec stores the software intent behind the work: the problem, hypothesis, scope, acceptance criteria, and success metrics that downstream tools should preserve.
I'd love for this standard to be broadly adopted, which means it must be broadly owned by the builder community.
Founders, PMs, engineers, designers, researchers, AI builders: please contribute examples, critiques, section changes, parser implementations, validator improvements, and integrations with GitHub, Jira, Linear, Figma, OpenSpec, Spec Kit, and agent workflows. (link below on how to contribute)
If you have scars from writing product docs that looked aligned but failed during execution, those scars belong in the standard.
My goal is for ProductSpec to become the open source format for software intent before implementation.
(links below)
"चीन ने मेरिट और इक्विटी को प्राथमिकता दी! ज़बरदस्त सरकारी क्षमता विकसित की, एक ही पीढ़ी में लाखों लोगों को गरीबी से बाहर निकाला!
भारत ने मेरिट के बजाय इक्विटी को प्राथमिकता दी!
और नतीजा?
-60% कोटा
-औसत दर्जे के संस्थान
-पूरी व्यवस्था पर क्रीमी लेयर का कब्ज़ा"
गुरचरण दास🔥🔥
I enjoyed putting together this series.
Part III is out today, on the hardest of the three problems: not getting knowledge in, or keeping it there, but pulling it back out when you actually need it.
(1/2)
In theory, consistency is about being disciplined, determined, and unwavering.
In practice, consistency is about being adaptable. Don't have much time? Scale it down. Don't have much energy? Do the easy version. Find different ways to show up depending on the circumstances. Let your habits change shape to meet the demands of the day.
Adaptability is the way of consistency.
To the public: "E20 fuel is safe and fully tested."
To the Supreme Court: "It’s just an experiment, we’ll know results next year."
The government completely lied about E20 readiness. They rushed this rollout to serve vested interests and corporate logistics, leaving millions of everyday vehicle owners to act as guinea pigs in a forced, destructive trial. Complete betrayal of public trust. #EthanolScam
https://t.co/yc1K1mB6xM
Aniket Patil a small entrepreneur has been distributing tea to the protesters at Jantar Mantar.
Yesterday, three Delhi Police personnel tracked down his home and godown and visited them for an inquiry.
Why Delhi Police is so interested in our chai-pani?
A simple cheat code for young people:
Do whatever it takes to become excellent at your first few jobs.
The people you work with will open doors for you for the next forty years.