Simranjeet Singh

engineer building and posting

[Simranjeet Singh @singhs020]

@samuelrdt This is great. Thanks for sharing

[Y Combinator @ycombinator]

Software for Agents
@aaron_epstein

The next trillion users on the internet won't be people. They'll be AI agents, and they're already doing real work on top of software that was designed for humans clicking buttons.

Every major category of software needs to be rebuilt for agents as first-class citizens, and that won't come from incumbents.

[Simranjeet Singh @singhs020]

Th new age companies are going to sell outcomes, done fotlr you service but with the power of the AI. AI is the differentiating factor in here.

[Y Combinator @ycombinator]

AI-Native Service Companies
@gustaf

The total spend on services is many times larger than the spend on software, and a lot of those services are already outsourced, which makes them easier to replace with an AI-native product.

We're excited about companies that don't sell a tool to help you do the work: they just do the work.

[Simranjeet Singh @singhs020]

This is great news if you are building agents and need secure connectivity

[Vercel @vercel]

Vercel Connect is now generally available.

Give your apps and agents secure access to @slackhq, @linear, @github & 100+ other services.

• Short-lived, scoped access tokens
• Token and trigger observability
• RBAC and audit trails

https://t.co/3JUlBz3ddo

[Aviral Bhatnagar @aviralbhat]

Interesting areas for Indian startups to build in:

- Trusted Platform for Used Goods
- GPS-Denied Drones
- AI Wealth Manager for Middle Class
- Discovery-Led Fashion Marketplace
- AI Coaches for Professionals
- Screen-Free Intelligent Toys
- Infrastructure for AI agents
- Specialty-Focused Micro Clinics
- Vertical AI for Hardware Design
- Smart Home Electronics
- Bio-Manufacturing for Specialty Chemicals
- Climate Resilient Cooling
- Regional Nutrition Brands

Incredible decade to be an entrepreneur in India

[Simranjeet Singh @singhs020]

@gregisenberg Absolutely the agent experience is going to be the next wave of applications coming up. Initially we have to think about only user experience and now if you are not thinking about agent experience you are going to miss a lot of opportunities in future.

[Simranjeet Singh @singhs020]

@HelloVyom This is nice. Great 👍

[Simranjeet Singh @singhs020]

Make something people want.

Thats what I am going to do now. All of this will be experiments and various side hustles in various industries. I am going to post everything raw and will try put out the thought process out.

Goal is to learn and have fun.

[Simranjeet Singh @singhs020]

If your systems enable experimentation, quick rollouts, and compliance guarantees — you’re not just writing code.

You’re shaping the product.

[Simranjeet Singh @singhs020]

Engineers Who Understand Product Are 10x More Valuable

You don’t need to own the roadmap to care about the outcome.

I’ve seen firsthand how engineering impact grows when you understand what product teams are really solving:

[Simranjeet Singh @singhs020]

🔍 What’s the real user constraint behind this “urgent” change?

🧭 Can the system enable iteration, not just meet current requirements?

📉 Can we reduce risk through tech — not just process?

Product velocity is often an infra problem in disguise.

[Simranjeet Singh @singhs020]

I’ve learned to ask during reviews:

> “Can this decision survive change — or at least absorb it without pain?”

That question alone has saved months of future rework.

[Simranjeet Singh @singhs020]

Not Every Architectural Decision Needs to Be Permanent

Good architecture solves the problem. Great architecture adapts when the problem changes.

One of the biggest mindset shifts in my career:
Not every architectural decision needs to be permanent.

[Simranjeet Singh @singhs020]

You can start with fewer layers — and decouple later

🔁 The ability to change gracefully matters more than getting it perfect

Great infra doesn’t just scale.
It evolves — because the business, users, and context will too.

[Simranjeet Singh @singhs020]

Clever systems get praise in design reviews.

Clear systems survive everything after.

[Simranjeet Singh @singhs020]

Engineering Clarity > Engineering Cleverness

The longer I build systems, the more I value clarity over cleverness.

It’s tempting to reach for abstractions, generics, or design patterns that make us feel smart.
But the best codebases I’ve worked with shared one trait:

[Simranjeet Singh @singhs020]

Why does this matter?
Because clarity scales. Cleverness doesn’t.

Clarity enables faster onboarding

Clarity makes debugging predictable

Clarity makes compliance provable

Clarity helps infra evolve without fear

[Simranjeet Singh @singhs020]

Good engineers optimize code.
Great engineers debug thinking.

[Simranjeet Singh @singhs020]

Your System Design Is Only as Good as Your Mental Models

Most bad architectures don’t start with bad code — they start with bad assumptions.

We often treat system design like a diagramming exercise. But underneath every scalable system is a set of mental models that shaped it:

[Simranjeet Singh @singhs020]

But they drive everything from scalability to developer experience.

One of the biggest shifts in my career was learning to design from models, not modules — to align the system with:
How the business flows
Where the real latency lies
What can (and will) go wrong