Amit Parashar

Curious, hungry for knowledge, learner and an executor. RT's are not endorsements.

[Mahesh 🇮🇳 @invest_mutual]

Super stuff. Do listen to him.
The points he makes are 👌👌👌

[Ritesh Jain @riteshmjn]

Brilliant piece.

if there is one thing only which you can read today then this is the one worth reading.

[Zeb Evans @DJ_CURFEW]

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.

[$@M @SAMTHEBESTEST_]

Number of memes #AkshayKumar gave in this clip are higher than the combined total of 4-5 actors 😃🙏

[Neo Kim @systemdesignone]

If you want to get started with system design, then learn these 12 concepts:

1 How RPC Works:
↳ https://t.co/yeIgcmAxQx

2 Idempotent API:
↳ https://t.co/afe7ACuSYE

3 Saga Design Pattern:
↳ https://t.co/2CffTodOHL

4 How Bloom Filters Work:
↳ https://t.co/ntZXq7LxVn

5. How Consistent Hashing Works:
↳ https://t.co/7d6EipPcKF

6. Service Discovery:
↳ https://t.co/BcL3tgxx1u

7. Microservices Lessons From Netflix:
↳ https://t.co/XgS7VQoBFv

8. Modular Monolith Architecture Explained:
↳ https://t.co/VVV6v3KGHJ

9. How Databases Keep Passwords Securely:
↳ https://t.co/KSfIhpAT2j

10. Best Practices for API Design:
↳ https://t.co/I2ejJ0kbYq

11. API Versioning - A Deep Dive:
↳ https://t.co/OHAtKSUgVN

12 How JWT Works:
↳ https://t.co/SZXXrlBsWH

What else should make this list?

===

👋 PS - Want my System Design Playbook for FREE?

Join my newsletter with 200K+ software engineers now:
→ https://t.co/ByOFTtOihX

===

💾 Save & RT to help others get started with system design.
👤 Follow @systemdesignone + turn on notifications.

[Neo Kim @systemdesignone]

7 most effective techniques to scale a database

&gt;vertical scaling
&gt;caching
&gt;horizontal scaling
&gt;query optimization
&gt;connection pooling
&gt;concurrency control

what else should make this list?

[Ben Dicken @BenjDicken]

Consistency is one of the biggest challenges in distributed databases.

These systems can ensure all servers have an in-sync view of the data at two points in time:

- When *reading* (read-repair)
- When *writing* (ex: hinted-handoff)

How this works:

[Ashutosh Maheshwari @asmah2107]

System design concepts I’d master if I wanted to crush it.

Bookmark this.

1.Consistent Hashing
2.Sharding
3.CAP Theorem
4.Quorum Consensus
5.Leader Election
6.Raft & Paxos
7.Gossip Protocol
8.Vector Clocks
9.Load Shedding
10.Circuit Breakers
11.Backpressure
12.Tail Latency Reduction
13.Bloom Filters
14.HyperLogLog
15.Reservoir Sampling
16.Split-Brain Resolution

Follow @asmah2107 to uplift your system design game.

[Leonie @helloiamleonie]

What goes into the system prompt vs. what goes into an Agent Skill?

Agent’s system prompt is for identity, constraints, and persistent context.
• What the agent is and what it should always or never do
• How it should generally approach problems (reasoning style)
• Persistent context needed for every interaction

Agent Skills are for capabilities the agent can choose to invoke when relevant.
• Dynamic context
• Performing actions with side effective (e.g., calling APIs)
• Anything that’s optional depending on the situation

Practical rules of thumb:

If it’s a specific action the agent does, it goes in a skill.
If it’s the identity of who the agent is and how it thinks, it goes in the system prompt.

If it changes per-request, it goes in a skill.
If it's stable across all requests, it goes in the system prompt.

[Joe Tippens @JoeTippen]

This is nothing short of a miracle.

Dr John Campbell breaks down the study of an 83yr old woman with stage 4 breast cancer that had metastasised to the liver, spine and bones.

Usually a death sentence.

She took a daily dose of 222mg of FenBen for 8 months. Which normalised her liver enzymes. The tumor marker dropped from 316 to 36.

There was an absence of any abnormal metabolic activity indicative of cancer. Please like, share, and follow my page. Information like this need to be heard and seen by everyone.

[The Eagle flies free @Fa21519230]

🚨🚨 Nuevo estudio de 197 pacientes con cáncer tratados con Ivermectina (25 mg) + Mebendazol (250 mg) promete...
Después de 6 meses:
• 84.4% tuvo beneficio clínico
• 48.4% tuvo reducción del tumor o ninguna enfermedad detectable
• 86.9% completó el tratamiento con efectos secundarios leves
Dr. Peter McCullough.

[Joe Tippens @JoeTippen]

Don’t tell Pfizer

🚨 Stage 4 Cancer... GONE in 3 Months — Naturally!

A 73-year-old woman was told there was no cure. Stage 4. “Nothing we can do,” doctors said.

👉 But just 90 days later… her scans showed NO disease detected.

What changed?
Her son went down the research rabbit hole on X and found my posts on IP6 (Inositol Hexaphosphate), juicing, Mesima mushrooms, and Ivermectin.

Here’s what she did ⬇️
• 🥄 IP6: 2 scoops, twice a day on an empty stomach
• 🥕 24 oz carrot juice daily (+ some other juices)
• 🍄 A bit of Mesima mushroom & Olive leaf
• 💉 3 immunotherapy sessions (docs said it wouldn’t cure her)
• 💊 Ivermectin: added as support — we’re seeing more and more remarkable responses when it’s included 👏

⚡ No chemo. No radiation. No Fenben.

And guess what? The cancer disappeared.

This isn’t a one-off story. I’ve been receiving multiple reports of stunning cancer reversals using these exact protocols — especially IP6, juicing, and Ivermectin.

There are also published studies and case reports showing the same thing:
👉 These natural compounds have powerful anticancer effects.

People deserve to know this.
(But shhh… don’t tell Pfizer, or they might “regulate” them 😉)
Share, like, and follow my page. There is a need for every patient to know about this.

[PunsterX @PunsterX]

Party with the lowest percentage of women MPs in this list, is making the most noise about nari shakti.

The most they've ever done for nari shakti in politics is-

Making 12th pass Smriti Irani the HRD minister in 2014, even after she lost the LS election from Amethi.

[Jasper Truth 🇺🇸 🇨🇦 @Jasper_Truth]

IVERMECTIN AND MEBENDAZOLE - 84% BENEFIT IN FIGHTING CANCER!

[Roan @RohOnChain]

This 2 hour Stanford lecture will teach you more about how LLMs like ChatGPT &amp; Claude are built than most people working at top AI companies learn in their entire careers.

Bookmark this &amp; give 2 hours today, no matter what. It'll be the most productive thing you do this week.

[DeepLearning.AI @DeepLearningAI]

Vibe coding is fast. It’s also unpredictable. Spec-driven development is the alternative: define what to build in a clear spec, then let your coding agent implement it.

In our new spec-tacular short course with @JetBrains and @JetBrains_Edu, you’ll learn how to:

⚙️ Write project constitutions and feature specs
⚙️ Guide agents with a plan–implement–verify workflow
⚙️ Keep outputs aligned with your intent across sessions

Taught by @paulweveritt.

Join in for free ➡️ https://t.co/bjrpN2YgRp

[Andrew Ng @AndrewYNg]

New course: Spec-Driven Development with Coding Agents, built in partnership with @jetbrains, and taught by @paulweveritt.

Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way.

A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity.

Skills you'll gain:
- Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start
- Plan, implement, and validate features in iterative loops using a spec as your agent's guide
- Apply the same repeatable workflow to both new and legacy codebases
- Package your workflow into a portable agent skill that works across agents and IDEs

Join and write specs that keep your coding agent on track!
https://t.co/hI4GwuvhtN

[News Algebra @NewsAlgebraIND]

Family gifts their house help an air cooler ahead of the summer season.

OWNER : Sister, I have something for you

HOUSE HELP : What is it?

OWNER : "You take care of us, so it’s our duty to take care of you" 🥰

[Ronit Pereira @CAronitpereira]

Remember this scene

A shareholder named Abhishek Kalra holding just 1 share lectured the management of GKB Lenses for 3 minutes. 😂

Incredible