Stani

Professional Software Engineer

[Stani @stanislav]

@badlogicgames Just a little heads up, in the screenshot the delivery address is visible. Not sure if this is sensitive information of yours.

[Stani @stanislav]

@tharshan_09 @nbaschez @hnshah @plannotator Had the same question 😅

[Stani @stanislav]

@badlogicgames Pokemon Go: hold my beer 🍺

https://t.co/dffy1oGOAK

Cheers. 🍻

[Stani @stanislav]

Coinbase:
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.

[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

[Stani @stanislav]

@micLivs @badlogicgames Very interesting approach. I've tried to go a similar route by literally wrapping official n8n nodes. With the hope of using battle tested integrations by the n8n community. What is your approach of verification?

Btw, here is the cli/repo:

https://t.co/mYI5rtqo7U

[Peter Pang @intuitiveml]

https://t.co/oWr2pTk4Hu

[Stani @stanislav]

Stop writing MCP servers for every integration your agent needs.

https://t.co/edOcxfOhTb

#AIAgents #CLI #n8n #DevTools #automation

[Stani @stanislav]

🚀 Releasing nathan-cli

One CLI. 400+ integrations. No proxy, no cloud, no cost, runs 100% local.

npm install -g nathan-cli

GitHub, Slack, Jira, Airtable, HubSpot, OpenAI… all of n8n’s node ecosystem, directly from your terminal.

[Stani @stanislav]

Perfect for AI agents with shell access.
Let them discover tools autonomously:

nathan plugin list → what’s available
nathan describe slack → what can I do?
nathan describe slack message post → what params?

Self-documenting. No custom tool definitions needed.

[Stani @stanislav]

@garrytan Agree. But there is already an official playwright cli, no need to vibe code it:

https://t.co/c9nxREGT9O

[Stani @stanislav]

@pbakaus @trq212 Maybe because of this?

https://t.co/KRYzchphB6

[Boris Cherny @bcherny]

👋 we recently changed the default effort to medium to better balance intelligence with speed, based on median usage we were seeing in the wild.

You can change it anytime in the /model selector if you prefer low effort (faster) or high effort (more intelligence). The setting is sticky and will persist for your next session.

If you’ve changed effort to high already, can you double check you’re on the latest version, and that your CLAUDE.md’s (in /memory) don’t have confusing/conflicting instructions? That’s the most common cause.

[deleted a previous post where I accidentally said default is high, it’s early and I haven’t had coffee..]

[Stani @stanislav]

@tankots @WisprFlow Wispr Flow

[Stani @stanislav]

@slicknet rem should be the final result, because base font-size is adjustable either system wide xor through browser settings for a11y reasons. But having it in rem in the source is rather unpractical because design world is based on px values and floats are harder to grasp. Depends.

[Stani @stanislav]

@KiwiDenny It's so wrong. For each of his tweets an former employee can come back.

[SaltyAom @saltyAom]

GraphQL to TypeScript type, no code gen.
Written purely in TypeScript type.

With Prisma-like query syntax fully type-safe.
Should cover almost all of the GraphQL specs, now.

Here's a demo.

[Stani @stanislav]

@mattpocockuk @TkDodo DRI joined the conversation. ✌️

[Stani @stanislav]

@mtaushb Touché

Zufällig einen Link dazu zur Hand?

[Stani @stanislav]

@_ketterechts Bremsleitung im Rahmen ggf.

[Stani @stanislav]

@terronk Usual practice in germany ✌️