Siddharth Chopda

Building operational leverage @actuatelab

[Siddharth Chopda @siddharthtwt]

https://t.co/xKURwmTEdO

[Siddharth Chopda @siddharthtwt]

Can't agree more.

When computers became part of our everyday lives, the goal was never to replace people. It was to take repetitive, time-consuming work off our plates so we could focus on work that actually needed human judgment, creativity, and problem-solving.

AI is no different.

It's not about replacing humans. It's about giving us back our time, so we can spend more of it doing what only humans can.

[Deedy @deedydas]

The world is deeply unfair.

Some of the most talented people I know are stuck in dead end desk jobs while some of the snarkiest narcissistic tyrannical workhorses are in positions of great power.

This has always greatly saddened me.

After a lot of analysis, I think there are 5 reasons this happens:

1. Refusal to believe / fear of failure. Loss of belief that where there is a will (to enact change), there is a way e.g. “I am just a cog in the wheel. If I say something, no one will listen.” or “if I do this, I will upset somebody”

2. Lack of purpose. You don’t really understand what you’re fighting for and what you believe in. You fight for inconsequential, often selfish, goals. e.g “Will doing this get me a promotion? Should I completely change everything to do this other project cause it will get me a promotion?”

3. Lack of self awareness. I will stand up to this thing I believe in and they will listen to me. e.g intern saying: “why doesn’t the ceo like my view on company strategy?”

4. Refusal to play. The failure to acknowledge that your worldview is only as powerful as your ability to influence others of your worldview OR a complete repudiation of the will to interact with those who don’t share your worldview e.g. “these guys just do what they want. They won’t listen to me. what will happen if I do this?”

5. Refusal to strategize or concede. The unwillingness to play and win a side quest that will ostensibly further your vote because you find the interim goal pointless. Or the inability to concede a battle to fight the war. e.g. “this direction is wrong. I need to fight it (even though it’s a small issue)”

Almost everyone who is bitter or feels stuck in their career boils down to one of these 5 failure modes 1, 2 and 3 are the most common. Many suffer consequences of 2-5 and end up in 1. I’ve personally seen some of my sharpest friends land up in 1 because they just don’t believe they can win.

One privileged part of my job is getting to interact with people who are willing to, against all odds, believe in something heretical, know why it’s important, know what needs to be done to make it real, do it, and make side quests to get it done. I think it applies to everyone doing anything.

[Siddharth Chopda @siddharthtwt]

AI has changed everything. It can write, code, design, and build faster than ever, lowering the barrier to entry for almost everyone.

But standing out? That's become much harder.

Today, when you show someone your work, the first question is often, "Was this AI-generated?" That says a lot about where we are. It's no longer enough to create something good you have to create something that feels original, thoughtful, and distinctly human.

The rules haven't changed. AI accelerates execution, but it can't replace judgment, taste, curiosity, or conviction.

In a world where everyone has access to the same tools, your greatest advantage isn't AI.

It's how you think.

[Siddharth Chopda @siddharthtwt]

AI systems are already converting operational bottlenecks to business leverage.

Once you start to build the correct systems.

You see exceptional results.

[Jaya Gupta @JayaGup10]

If you’re a software engineer worried about AI eating your job, become the person who can deploy, customize, evaluate, and operate *****open-source models***** inside companies. Organizations are finally optimizing for AI cost, privacy, and control and many will want this capability in-house.

[Siddharth Chopda @siddharthtwt]

If this happens! We're having a good future. 🙌

[Satya Nadella @satyanadella]

https://t.co/vLmiBKTtX3

[Siddharth Chopda @siddharthtwt]

A big misconception that most vibe coders have is their code will withstand all the production challenges!

But what they miss is; Having the idea of what's good enough.

That understanding to evaluate what's good enough only comes when you've been there done that.

Not saying, you should code on your own now in these times and age!

But whenever you get time, sit and write code or review and keep making yourself better.

Vibe coding alone won't make your application stand in production.

[Siddharth Chopda @siddharthtwt]

After working with freelance clients, serving as a founding engineer and product manager at a startup, and building enterprise software, I've realized that success ultimately comes down to two things: persistence and a relentless focus on creating business value.

Technology stacks evolve, tools change, and now coding itself is becoming increasingly commoditized through AI. But one thing remains constant: businesses reward outcomes, not activities.

The perspective that has consistently served me well is viewing every piece of work through the lens of business impact. Instead of asking, "What am I building?" I ask, "How does this create value?" Whether it's increasing revenue, reducing costs, improving efficiency, or enabling growth, the people who understand and deliver business value will always remain indispensable, regardless of how the technology landscape changes.

[Siddharth Chopda @siddharthtwt]

Delaying evaluation and observability while building a AI application is the biggest mistake which you can make.

If you're building vibe coded demos. You can skip this one!

But if you're serious Builder who has been solving problems with AI/LLMs. Evaluation and observability is the thing you need to focus on before you move to build complex workflows.

[Siddharth Chopda @siddharthtwt]

In the beginning, I focused a lot on how I can learn the best frameworks and libraries so I can keep up with everything. But the more I learn about tech,

I realise that technology is just a tool which you use to solve real problems. If you keep chasing just cool and new tech, you won't get real results!

[Siddharth Chopda @siddharthtwt]

The deeper I go into AI engineering, the less I think the challenge is "using models."

The challenge is building systems around them.

Models will improve.

The companies that win will have strong execution layers, knowledge layers, evaluation systems, and developer experience around those models.

That's the part I'm exploring with Proto.

[Siddharth Chopda @siddharthtwt]

Building Proto has changed the way I think about software.

For years, I built traditional web applications where scaling felt predictable:
More users → more infrastructure.
But AI products introduce a completely different set of constraints.

And I don't think enough engineers talk about it.

[Siddharth Chopda @siddharthtwt]

While building Proto, one lesson became obvious:

You shouldn't treat LLM calls as business logic.

They're infrastructure.

That's why I started separating execution from model providers entirely.

Chains can be tested without hitting an LLM.
Providers can be swapped.
Capabilities can evolve independently.
The system becomes easier to reason about.

[Siddharth Chopda @siddharthtwt]

Everything boils down to your taste and selection if you are in tech now.

Ai news is coming every hour, if not days
But humans are not designed to context switch that fast and nor do we have that steep learning curve to learn every AI tool.

Knowing enough which makes your work easier, faster and better.

That's what you need to do!

[Siddharth Chopda @siddharthtwt]

Setting intentions for the week always worked for me, But I never shared it online, here's my intent;

- Studying the top 10 people on Ai on X and staying updated with whats going on.
- Building proto's Rag layer a little more adavance ( Hybrid search, perhaps more advance stuff)
- Studying the case studies of how robust and reliable systems are built at scale.