Ee Sala Nu Cup Namdu! ❤️🔥🏆
Welcome to the RCB Era, ladies and gentlemen! 😎
You waited, you believed and you stayed… this one’s for you again, 12th Man Army! 🥹❤️
#PlayBold#ನಮ್ಮRCB#IPL2026
🚨 Suresh Raina on alleged pitch rigging ahead of the final:
"The final should have been at Chinnaswamy. RCB are the defending champions, and if not Bengaluru, then a neutral venue like Raipur would have made more sense.
Instead, the curator seems to be following GT's preferences. The pitch has been prepared perfectly for Gujarat's strengths. This looks like pure rigging and an unfair advantage in a match of this magnitude."
IT Before 2022: Jira tickets, Postman collections, Java development, manual testing, Excel sheets, weekend deployments, production support, long meetings.
IT After 2022: AI Agents, AI Automation, AI Coding, AI Startups, AI Resume Builders, AI Interview Prep, AI SaaS, AI Wrappers,
basically AI everywhere.
🚨 SUPREME COURT : "If both parents are IAS officers, why seek reservation?"
"The parents have studied, they are in good jobs, they are getting good income, and the children want reservation again"
"We will never get out of it"
"With educational and economic empowerment, there is social mobility"
"See, they should get out of reservation"
“design a RAG pipeline for 10M docs with zero hallucination”
apparently this was asked in a Google L5 interview round. came across it somewhere on the internet and honestly it’s a way more interesting system design problem than most classic distributed systems questions
1. ingest + normalize docs
- remove duplicates, standardize formats, extract metadata, maintain version history
2. hybrid retrieval (BM25 + embeddings)
- BM25 handles exact keyword matching while embeddings capture semantic meaning
- semantic search alone usually struggles with precision at massive scale
3. ANN retrieval + reranking
- ANN (Approximate nearest neighbor ) quickly pulls top candidate chunks from millions of docs
- then a reranker rescoring step improves relevance by deeply comparing query vs retrieved chunks
4. source confidence scoring
- every retrieved chunk gets scored based on freshness, trust level, overlap and retrieval consistency
- low-confidence context should never heavily influence generation
5. constrained generation
- the model is only allowed to answer using retrieved context (nothing new to be invented outside of the retrieved context)
6. citation-backed responses
- every major claim links back to exact chunks, documents or timestamps
7. hallucination fallback layer
- if retrieval confidence drops below a threshold: “insufficient evidence found”
8. continuous evals
- run adversarial queries, retrieval recall benchmarks and hallucination tests continuously
9. caching + memory layer
- cache high-frequency enterprise queries and retrieval paths (improves latency and output)
10. observability everywhere
- trace retrieval paths, chunk rankings, token attribution and failure points
Also at 10M docs, retrieval quality matters more than the frontier model itself.
Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why.
First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it.
Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands.
Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition.
I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively.
THE 100X ORGANIZATION
The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago.
Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken.
The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems.
These roles will evolve. But waiting for that to happen naturally means falling behind now.
The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working.
THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS
— THE BUILDERS: 10X ENGINEERS
I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality.
Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment.
AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down.
Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed.
So who do you want orchestrating and reviewing code?
And how do you want your best engineers to spend their time?
If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code.
The new world is about enabling your 10x engineers to become 100x.
The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated.
I call this the great reckoning of AI coding, and every company will face this soon if not already.
More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well.
— THE BUILDERS: 10X PRODUCT MANAGERS
Product management and design roles are merging.
Designers that have customer focus, become more like product managers.
And product managers that have intuition for UX become more like designers.
The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results.
The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy.
Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on.
To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production.
Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck.
That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time.
— THE SYSTEM MANAGERS
Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp.
The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world.
You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is.
— THE FRONT-LINERS
In a world that will become saturated with AI communication, the human touch will matter more than anything to customers.
This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings.
One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers.
REWARDING 100X IMPACT
In a world where companies are able to do so much more with less, where does that excess money go?
In our case, much of the savings in this new operating model will flow directly back to those that enabled it.
We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them.
You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace.
Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems.
THE FUTURE
Nearly every company will make changes like these. The ones that do it proactively will define what comes next.
The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago.
ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.
The NEET paper leak would probably have stayed buried forever if a school teacher from Sikar had not refused to stay silent.
Shashikant Suthar, a chemistry teacher from Rajasthan, was shown a “guess paper” by one of his neighbors after the NEET exam. That PDF had reportedly been circulating in Telegram groups for weeks.
Out of curiosity, he matched it with the real exam paper.
The result was terrifying.
Around 140 questions were identical. Same sequence. Same wording. Even punctuation marks matched.
He rushed to the local police station expecting immediate action.
Nobody listened.
No FIR.
No urgency.
No investigation.
But instead of giving up, he kept escalating the matter emailing the NTA, PMO, President of India, and CBI while continuously raising the issue online.
Only then did the system move.
Rajasthan Police formed a Special Operations Group. What initially looked like a small leak soon exploded into a nationwide examination scam connected across multiple states.
The case eventually reached the CBI. NEET was cancelled. And investigators uncovered an organized network of professional paper leak operators.
This entire scandal was exposed because one ordinary teacher decided that remaining silent was not an option.
Sometimes one honest citizen is more powerful than an entire broken system.
Serious question.
For 20 years, a "Software Engineer" was someone who spent thousands of hours mastering complex syntax, logic, and architecture.
Now, a 19-year-old can vibe-code a production-ready SaaS in a weekend using plain English and a $20 Claude subscription.
What does the title "Software Engineer" even mean right now?
I’ve posted before about our family’s coffee plantation in Kodagu, which my younger sister manages, and which we’ve come to regard as our adopted ‘ancestral home.’
She just sent me this clip: a herd of elephants marching this morning from one gate of the estate (the Arabica bushes side) through to the other gate across the road (the Robusta side.)
This isn’t some new phenomenon caused by habitat encroachment. These majestic visitors have been dropping by for decades, usually to raid the jackfruit trees on the property.
But this time they seem to be strolling through the main gates with such confidence that it almost feels as if they had received a formal invitation for tea and snacks…
You get the feeling they know the plantation was always theirs, and we’re merely temporary tenants…
@anandmahindra Allow the forests to regrow at least in their path. You will set an example to other coffee planters to provide these beautiful beings a safe and natural passage. I don’t think such an action will make any difference to your wealth.