Consultant
Tracking infrastructure, urban planning, startups, and economic development.
Thoughts on building a better Hyderabad and a more competitive India.
🚨#ALERT: GEETANJALI JI’S HAIR PULLED BY DELHI POLICE, ASSAULTED.
A 12 YEAR OLD GIRL’S HEAD HAS BEEN BROKEN. 40-50 OTHER HEADS BROKEN!
@DelhiPolice WHAT IS GOING ON!?
@dravishakatoch I am from a startup background infact from a vc background and a lot more people like me showed up for the Hyderabad protest . More than 600 people from all walks of life showed up . People are showing up . People are angry . #hyderabadprotest#cjp
19 दिन का अनशन लगभग 9 किलो वज़न कम फिर भी सोनम वांगचुक अपने संकल्प पर डटे हुए हैं,
सवाल सिर्फ़ एक व्यक्ति का नहीं, बल्कि उन मुद्दों का है जिनके लिए वह आवाज़ उठा रहे हैं।
Satya Nadella just published the most important essay in enterprise AI this year. Also the most self-serving.
He argues companies "pay for AI twice." Once with cash. Again with institutional knowledge: every prompt, every correction, every "no, we handle it THIS way" flowing to the model provider. He calls it the Reverse Information Paradox.
He's right. Now look at who profits most from this paradox.
GitHub Copilot sits inside your IDE. Every accepted suggestion, every rejected completion, every edit after accepting is institutional knowledge becoming training signal. Azure OpenAI Service runs your proprietary data through models Microsoft co-owns. Microsoft 365 Copilot reads your emails, documents, Teams messages.
Microsoft operates the single largest surface area for collecting enterprise AI "exhaust" on earth.
He calls it "ironic" that providers claim fair use for training but impose restrictive distillation terms and reserve the right to learn from customer data. He's describing his own partner's terms of service.
Re-read the essay with that context.
Nadella describes a problem his products helped create. Then positions his infrastructure as the fix. The "trust boundary"? Azure with customer-managed keys. "Distributed learning infrastructure"? Azure ML in your tenant. He quotes Palantir's Karp about "controlling the means of production." Palantir is an Azure partner.
The 5 C's (Control, Capability, Choice, Cost, Compound) aren't a framework. They're a product roadmap dressed in Hayek and Arrow.
The essay is correct about the problem. But the implied fix, build your trust boundary on Microsoft's stack, is the same trade with better language. You're renting the containment wall from the company your knowledge needs containing from.
A real trust boundary means infrastructure you own. Model gateway you control. Private evals your team defines. Immutable logs in your VPC. Open-source components you can fork if the vendor changes terms tomorrow. We built this. Runs inside the customer's perimeter. We can be fired and the infrastructure stays.
That's the difference between a trust boundary and one with an asterisk.
When you built yours, was the first vendor you excluded the one selling you the most tools?
Yesterday’s traffic collapse exposed a larger challenge facing Hyderabad
As employment, residential density & vehicle ownership continue to grow, transport and drainage infrastructure must expand as well.
The issue isn’t rain. It’s infrastructure planning in pace with growth
@adityapuranam8@GHMCOnline@CommissionrGHMC Infrastructure failures become especially costly when they occur in high-traffic employment corridors.
Beyond repairs, it may be useful to publish root-cause analyses and preventive maintenance plans so similar failures can be avoided before the peak monsoon period.
@DonitaJose Absolutely agree
Flyovers often solve a local bottleneck but don’t necessarily reduce corridor-wide congestion. Without stronger public transport and better land-use planning, traffic is often redistributed rather than eliminated.
@PrasadPeketi The bigger question is whether infrastructure capacity is being planned alongside density.
Higher FSI and concentrated employment can work, but only if transport, drainage, water supply and public transit scale at the same pace. This rain exposed the gap
@Kilaruness The real test of a city’s infrastructure isn’t how it looks on a drone shot, it’s how it performs under stress.
A few centimetres of rain shouldn’t bring a major economic corridor to a standstill. Resilience needs to become as important a metric as growth.
Every year we discuss the same problem.
The goal should not be managing traffic after waterlogging occurs.
The goal should be preventing waterlogging in the first place.
Hyderabad deserves infrastructure that matches its economic importance.
Hyd is one of India’s premier tech hubs. Yet ~4 cm of rain led to the IT corridor to a standstill, with commuters spending up to 4 hrs travelling a few kilometres.
The issue isn’t the rain.
The issue is urban planning.
@TelanganaCMO@revanth_anumula#Hyderabad#Infrastructure
Part 2. A city generating billions in economic output can’t rely on infrastructure that fails during routine monsoon. We need
• Modern stormwater drainage network
• Regular desilting of nalas
• Flood resilient road design
• Better coordination bw road, drainage & utility work
For all travelling to thailand, malaysia - don't ever travel #Airasia - broken bags , they won't reimburse even with insurance, dirty seats and extremely delayed flights . Not a good first experience.