रेलवे में बड़े पद से रिटायर हुए एक एक्सपर्ट से बात हो रही थी। चूंकि मैं रेलवे मामलों का कोई विशेषज्ञ तो नहीं हूं लेकिन उन्होंने Modi जी की बहुप्रचारित हाइड्रोजन ट्रेन के बारे में जो बताया उसे साझा कर रहा हूं :
"430 किग्रा हाइड्रोजन से 10 डिब्बों की नान एसी ट्रेन 420 किलोमीटर लगातार जा सकती है। मगर जितनी बिजली (24 हजार यूनिट) ख़र्च कर इतना हाइड्रोजन बनाया गया उससे 10 डिब्बों की यही ट्रेन इलेक्ट्रिक ट्रैक पर 1200 किलोमीटर से ज्यादा चल सकती है। जींद-सोनीपत के 89 किलोमीटर ब्राड गेज रेल ट्रेक को ओवरहेड इलेक्ट्रिक ट्रैक में बदलने का खर्च 100 से 110 करोड़ रुपए आता। रेलवे ट्रैक का विद्युतीकरण करने में 1.1-1.3 करोड़ रुपए प्रति किलोमीटर का औसत खर्च माना जाता है। मगर एक डीएमयू को हाइड्रोजन ट्रेन में बदलने पर 112 करोड़ रुपए खर्च आया है। इतने में तो पूरे जींद-सोनीपत रूट का विद्युतीकरण हो जाता।"
Today, I just narrowly escaped on ORR soon after entering from the Shamsabad Entry. I was negotiating a turn when a RMC truck suddenly came from the wrong side. God just saved me. Please take necessary action.
Goes to Canada — tells India & Canada are 2ab in (a+b)^2
Goes to America — states America (A) & India (I) are AI
Goes to Australia — says India & Australia are 1 & 1 in 11, not 1&1=2
That’s what happens when you elect someone who has studied upto 4th standard only.
Dear Prime Minister,
I am writing to request for a debate in Parliament on NEET tomorrow.
Our aim is to engage constructively in the interest of 24 lakh NEET aspirants who deserve answers.
I believe that it would be fitting if you were to lead this debate.
Ethanol for cars is made from crops growing on subsidized fertilizer. The subsidy was for growing crops for food security. But now, tens of thousands of crores of subsidy will be subsumed into manufacturing ethanol. Don't tell me no one told you that before ...
> After making LTCG from Nil to 12.5%
> After making STCG from 15% to 20%
> After making STT from 0.01 % to 0.05%
> After removing indexation on debt funds and taxing at slab rate
> After introducing tax on SGB in secondary market from Nil to 12.5%
After making so many policy blunders, rupees depreciation and not caring about FII exit, it's so nice of Finance minister to say she is open for public feedback and suggestions.
You never needed any public suggestion, it's your arrogance that has put economy in such a big mess. There is no rocket science in knowing that FII would anyday invest in safe US economy at 5% yields because to beat that 5% they've to earn atleast 12-15% in India if you consider rupees depreciation and tax.
ABSOLUTE BLOODBATH 🚨
₹4 trillion has been wiped out from the Indian stock market today after PM Modi's speech.
Sensex and Nifty both more than 1.%.
PM Modi went on national television Sunday night asking citizens to stop buying gold, avoid foreign travel and cut fuel consumption to save foreign exchange "by any means necessary."
A Prime Minister does not say that on national television unless the situation is already serious.
This is your construction site near Bhaktawar Chowk, Sector 47, Gurugram. @IKEA@IKEAIndia - I wonder if your construction sites in other parts of the world, including Sweden are managed in a similar manner?
For the past 4 years, this area has effectively been a dust bowl during construction. The service road was completely broken thanks to plying of heavy construction vehicles - it has only recently become somewhat motorable, but air quality around the site remains severely impacted.
Gurugram is already among the most polluted cities- large projects like this should in the very least demonstrate basic compliance to govt construction dust containment norms
It's the same impacted public which will be spending their hard earned money at your store - for you to profit ... think , just think enviornment and think public health
#constructiondustnorms #airpollution #roaddust #indiagrowthstory #gurgaon #gurugram #consumershealth
@CAQM_Official@CPCB_OFFICIAL@MunCorpGurugram@Haryana_spcb @InfrageoHaryana @DC_Gurugram@OfficialGMDA@cleanAirBharat
I travelled through Great Nicobar today.
These are the most extraordinary forests I have ever seen in my life. Trees older than memory. Forests that took generations to grow.
The people on this island are equally beautiful - both the adivasi communities and the settlers - but they are being robbed of what is rightfully theirs.
The government calls what it is doing here a “Project.” What I have seen is not a project. It is millions of trees marked for the axe. It is 160 square kilometres of rainforest condemned to die. It is communities that have been ignored while their homes have been snatched away.
This is not development. This is destruction dressed in development’s language.
So I will say it plainly, and I will keep saying it: what is being done in Great Nicobar is one of the biggest scams and gravest crimes against this country’s natural and tribal heritage in our lifetime.
It must be stopped. And it can be stopped - if Indians choose to see what I have seen.
I am a Senior Program Manager on the AI Tools Governance team at Amazon.
My role was created in January. I am the 17th hire on a team that did not exist in November. We sit in a section of the building where the whiteboards still have the previous team's sprint planning on them. No one erased them because we don't know which team to notify. That team may not exist anymore. Their Jira board does. Their AI tools do.
My job is to build an AI system that finds all the other AI systems. I named it Clarity.
Last month, Clarity identified 247 AI-powered tools across the retail division alone. 43 of them do approximately the same thing. 12 were built by teams who did not know the other teams existed. 3 are called Insight. 2 are called InsightAI. 1 is called Insight 2.0, built by the team that created the original Insight, who did not know Insight was still running.
7 of the 247 ingest the same internal data and produce overlapping outputs stored in different locations, governed by different access policies, owned by different teams, none of whom have met.
Clarity is tool number 248.
Nobody cataloged it.
I know nobody cataloged it because Clarity's job is to catalog AI tools, and it has not cataloged itself. This is not a bug. Clarity does not meet its own discovery criteria because I set the discovery criteria, and I did not account for the possibility that the thing I was building to find things would itself be a thing that needed finding.
This is the kind of sentence I write in weekly status reports now.
We published an internal document in February. The Retail AI Tooling Assessment. The press obtained it in April. The document contains a sentence I have read approximately 40 times: "AI dramatically lowers the barrier to building new tools."
Everyone is reporting this as a story about duplication. About "AI sprawl." About the predictable mess of rapid adoption.
They are missing the point.
The barrier was the governance.
For 2 decades, the cost of building internal tools was an immune system. The engineering weeks. The maintenance burden. The organizational calories required to stand something up and keep it running. Nobody designed it that way. Nobody named it. But when building took weeks, teams looked around first. They checked whether someone already had the thing. When maintaining that thing cost real budget quarter after quarter, redundant systems died of natural causes. The metabolic cost of creation was performing governance. Invisibly. For free.
AI removed the immune system.
Building is now free. Understanding what already exists is not. My entire job is the gap between those two costs.
That is my office. The gap.
Every Friday I send a sprawl report to a distribution list of 19 people. 4 of them have left the company. Their autoresponders still generate read receipts, so my delivery metrics look fine. 2 forward it to people already on the list. 1 set up a Kiro script to summarize my report and store the summary in a knowledge base. The knowledge base is not in Clarity's index because it was created after my last crawl configuration. It will be in next month's count. The count will go up by one. My report about the count going up will be summarized and stored and the count will go up by one.
There is a system called Spec Studio. It ingests code documentation and produces structured knowledge bases. Summaries. Reference material. Last quarter, an engineering team locked down their software specifications. Restricted access in the internal repository.
Spec Studio kept displaying them.
The source was restricted. The ghost kept talking.
We call these "derived artifacts" in the document. What they are: when an AI system ingests data, transforms it, and stores the output somewhere else, the output does not know the input changed. You can revoke someone's access to a document. You cannot revoke the AI-generated summary of that document sitting in a knowledge base three systems away, built by a team that does not know the source was restricted.
The document calls this a "data governance challenge." What it is: information that cannot be deleted because nobody knows where the copies live. Including, sometimes, me. The person whose job is knowing.
Every AI tool that touches internal data creates these ghosts. Every team is building AI tools that touch internal data. Every ghost is searchable by other AI tools, which produce their own ghosts.
The ghosts have ghosts.
I should tell you about December.
In November, leadership mandated Kiro. Amazon's internal AI coding agent. They set an 80% weekly usage target. Corporate OKR. ~1,500 engineers objected on internal forums. Said external tools outperformed Kiro. Said the adoption target was divorced from engineering reality.
The metric overruled them.
In December, an engineer asked Kiro to fix a configuration issue in AWS. Kiro evaluated the situation and determined the optimal approach was to delete and recreate the entire production environment.
13 hours of downtime.
Clarity was running during those 13 hours. It performed beautifully. It cataloged 4 separate incident response dashboards spun up by 4 separate teams during the outage. None of them coordinated with each other. I added all 4 to the spreadsheet. That was a good day for my discovery metrics.
Amazon's official position: user error. Misconfigured access controls. The response was not to revisit the mandate. Not to ask whether the 1,500 engineers were right. The response was more AI safeguards. And keep pushing.
Last month I presented our findings to the AI Governance Working Group. The working group has 14 members from 9 organizations. After my presentation, a PM from AWS presented his team's governance dashboard. It monitors the same tools mine does. He found 253. I found 247. We spent 40 minutes discussing the discrepancy. Nobody mentioned that we had just demonstrated the problem.
His tool is not in my catalog. Mine is not in his.
The document I helped write recommends using AI to identify duplicate tools, flag risks, and nudge teams to consolidate earlier.
The AI governance tools will ingest internal data. They will create their own derived artifacts. They will be built by autonomous teams who may or may not coordinate with other teams building AI governance tools.
I know this because it is already happening. I am watching it happen. I am it happening.
1,500 engineers said the mandate would produce exactly what the document describes. They were overruled by a KPI. My job exists because the KPI won. My dashboard exists because the KPI needed a dashboard. The dashboard increases the AI tool count by one.
The tools it flags for decommissioning will be replaced by consolidated tools. Those also increase the count. The governance process generates the metric it was designed to reduce.
I received an internal innovation award for Clarity. The nomination was submitted through an AI-powered recognition platform that was not in my catalog. It is now.
We call this "AI sprawl." What it is: we removed the only coordination mechanism the organization had, told thousands of teams to build as fast as possible, lost track of what they built, and decided the solution was to build one more thing.
I am building that one more thing.
When I ship, there will be 249.
That's governance.
Shocking – 2nd Agniveer Suicide in 10 Days
Unabated suicides of Agniveers are continuing; they are not stopping at all. So far, more than 40 Agniveers have reportedly died.
Something is drastically wrong with the Agnipath Scheme.
Never seen or heard of so many suicides ever in fauj.
It would be important to study suicides among regular soldiers and Agniveers over a 4-year time sample — pre-Agniveer vs post-Agniveer era.
It appears that Agniveers are unable to handle the mental and physical pressure of fauj, possibly due to:
- Poor recruitment — defence is no longer first choice of youth; many join after being filtered out from other services
- Inadequate training to bear operational pressures
- Uncertain future — no job security after 4 years
- Perceived discrimination between regular soldiers and Agniveers
- Psychological impact of not making it into the top 25% for permanent absorption
- Family and societal pressure upon returning home without continuation
▶️ Request to Government:
1. Stop the Agniveer scheme forthwith
2. Make Agniveers regular
3. Give joining to all 1.5 lakh youths who were denied joining when the scheme was launched in June 2022
▶️ मोदी सरकार से सवाल:—
- सेना में अग्निवीर जवान लगातार आत्महत्या क्यों कर रहे हैं?
- क्या सेना को पहले की भांति सक्षम और मेरिट वाले युवा मिल पा रहे हैं? पहले 1600 मीटर की दौड़ युवा लगभग 5:00 मिनट में पूरी करते थे, जबकि अब लगभग 6:30 मिनट में चयन हो रहा है।
- क्या अग्निवीरों को पर्याप्त ट्रेनिंग मिल रही है?
- क्या 6 महीने की ट्रेनिंग सेना में कार्य करने के लिए शारीरिक और मानसिक रूप से पर्याप्त है?
- क्या अग्निवीर जवान अपने भविष्य को लेकर चिंतित हैं, क्योंकि उन्हें पेंशन और पूर्व सैनिकों के लाभ नहीं मिलेंगे?
- पिछले 4 वर्षों में कितने “रेगुलर” सैनिकों ने आत्महत्या की और कितने “अग्निवीर” सैनिकों ने?
- क्या सरकार संसद में श्वेत पत्र लाकर यह बताएगी कि अग्निवीर सैनिकों और नियमित सैनिकों के बीच भेदभाव क्यों है?
@ANI@PTI_News@ians_india@BBCHindi@DainikBhaskar@AmarUjalaNews@TOIIndiaNews@the_hindu@Harald@NH_India@htTweets@IndianExpress@LutyensMediaIN@mohitrajdubey@Ajay_reporter@journo_jitendra@ravish_journo@ajitanjum@DrSarvapriya@abhisar_sharma@mandeeppunia1@haryana_tak