Aniket Sinha 𝕏

[Aniket Sinha 𝕏 @aniketsayz]

@arpit_bhayani so 2 lines of code per file?🤔

[Aniket Sinha 𝕏 @aniketsayz]

Just noticed that you can't edit your WhatsApp message if it was sent from a different device.
Interesting limitations.

[developing valhalla @valhalla_dev]

A pre-commit hook for Git that reads in the diff'ed code on a PR and quizzes you on it before you're allowed to open the PR.

You have to score an 85% or above on the quiz to open the PR.

This would fix 99% of complaints about slop PRs overnight.

[Aniket Sinha 𝕏 @aniketsayz]

@alokmalik @DanielGlejzner .md files are hard to maintain. Also why have two sources of truth. I have a better solution.
https://t.co/bkOOrOslWC

[Aniket Sinha 𝕏 @aniketsayz]

@DanielGlejzner This context problem of multi-repo polyglot codebases is solved now.
https://t.co/bkOOrOslWC

[Aniket Sinha 𝕏 @aniketsayz]

@Amank1412 Yes

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

@mehulmpt https://t.co/uHDKvle2fp @mehulmpt

[Aniket Sinha 𝕏 @aniketsayz]

@mehulmpt I am.
The goal is to make a cross-repo change functional.. basically an orchestrator with a bunch of sub agents.. one for each codebase

[Aniket Sinha 𝕏 @aniketsayz]

If you're in OpenAI Build Week, apply for the $100 OpenAI credits before you start building.

Mine just got approved.

Time to see what GPT-5.6 can do.

https://t.co/6Ps0m0d7Im

[Aniket Sinha 𝕏 @aniketsayz]

@mattpocockuk OTW to make the entire org self-explantory.
https://t.co/uhO8Iem5PO

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

@Hi_Mrinal What if an AI agent does it for you? Especially, when the incident spans to multiple repos.
https://t.co/uhO8Iem5PO

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

@kitlangton Built something similar for multi-repo orgs.
https://t.co/uhO8Iem5PO

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

@thdxr What if the AI agent opens the tested PR on its own.
https://t.co/uhO8Iem5PO

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

Prediction: Code generation won't be the moat. Engineering context will.

Imagine mentioning an agent in Slack and it understands the conversation, searches every repo, traces requests across services, investigates production, then opens a tested PR.

That's what I'm building.

[Aniket Sinha 𝕏 @aniketsayz]

@mehulmpt @bridgemindai It is common if you use agent swarms... Because the wall time covers all the agents in the swarm, but the api time is the sum of api time spent by each agent

[Aniket Sinha 𝕏 @aniketsayz]

@elastic This has been FlowMap's architecture from the beginning.

Hybrid search + cross-repo code intelligence + repository-aware reranking to give LLMs the right context across large, distributed codebases.

Open source: https://t.co/z0tMkMlD3b

[Aniket Sinha 𝕏 @aniketsayz]

@arpit_bhayani "Someone was too lazy to document their findings."

Or the answer is spread across 14 repos, 3 queues, and a database nobody owns.

FlowMap gives agents the system map they're missing.

https://t.co/z0tMkMlD3b

@arpit_bhayani

[Aniket Sinha 𝕏 @aniketsayz]

@ayushagarwal Coool. Curious how Squirrels handles cross-repo context and dependency discovery.

I built FlowMap ( https://t.co/bkOOrOslWC ) to automatically map service deps and code relationships across repos, and found that context becomes the hard part once agents move beyond a single repo

[Brian Armstrong @brian_armstrong]

This is an email I sent earlier today to all employees at Coinbase:

Team,

Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future.

Why now
Two forces are converging at the same time. We need to be front footed to respond to both.

First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth.

Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day.

All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core.

What this means
To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice?

- Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles.

- No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.

- AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role.

In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs.

To those who are affected
I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done.

All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information.

To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements.

Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters.

How we move forward
To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together:

Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it.

The Coinbase that emerges from this will be more capable than ever to achieve our mission.

Brian

[Aniket Sinha 𝕏 @aniketsayz]

@xoaanya It is making us faster. LLM assisted development and debugging is a breeze with flowmap-cli.
https://t.co/z0tMkMlD3b