Dragoș Mușetescu

639 posts

Dragoș Mușetescu banner
Dragoș Mușetescu

Dragoș Mușetescu

@dragosdm

I openly share my journey and lessons learned in building and growing businesses, with the hope of supporting and inspiring fellow entrepreneurs. #buildinpublic

Bucharest, Romania Katılım Nisan 2009
514 Takip Edilen499 Takipçiler
Sabitlenmiş Tweet
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
I'm thrilled by the positive feedback on my efforts to enhance our hiring process. Today, I finally wrote an article about it. What are your thoughts? Any areas you think I should delve into more deeply? lesscodeworks.com/how-we-redefin…
English
0
0
5
331
Thariq
Thariq@trq212·
HTML is the new markdown. I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why.
Thariq@trq212

x.com/i/article/2052…

English
895
1K
12.1K
4.4M
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
Have you tried pi? I was a long term Claude user and switched a few months ago. I find myself opening Claude less and less. How’s the in-terminal browser? I’m constantly switching from warp.dev to ghostty 😅. I have disabled all ai features in warp and since they’ve added side tabs it made a huge difference for my workflow
English
0
0
0
116
Amir Salihefendić
Amir Salihefendić@amix3k·
I think I’ve finally perfected my setup (ha! 😄) - cmux as the terminal. I get Ghostty, plus a bunch of other nice things like an in-terminal browser and sidebars - hunk as my core diff mechanism. I spend most of my time reviewing code, so optimizing for the diff experience makes a lot of sense. I am finding things like Cursor/Zed to be too bloated - Codex or Claude Code with a custom AGENTS.md and a few custom skills What am I misisng?
Amir Salihefendić tweet media
English
45
8
289
33.1K
Alex Lieberman
Alex Lieberman@businessbarista·
I want to start an AI community for executives. This will be a space for people to share killer use cases, agentic workflows/agents, post-AI org structure, AI governance, AI training/enablement, change management, and more. Comment “AI-native” if you want to join.
English
1.8K
33
1.1K
182.9K
Armin Ronacher ⇌
Armin Ronacher ⇌@mitsuhiko·
Why does everybody want managers to be ICs? Please someone explain this to me from first principles.
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

English
272
23
1.5K
443.9K
Amir Salihefendić
Amir Salihefendić@amix3k·
At Doist, we’ve always had a hands on leadership style. It’s also quite common in other orgs (e.g., Apple, Stripe). From our handbook why we do this: # Hands-on leadership Doist's tenets relating to hands-on management are: * Our leaders are functional experts who also do hands-on work. * Leadership is a parallel track that you join if you enjoy and are good at working with people; these are the core incentives. The core arguments of our way are the following: * Some people move into leadership roles because they want to advance in their careers, not because they have a passion for the job. The usual result is awful leadership. * We want you to lean on what you enjoy and what you are good at without feeling like you're making a compromise. And we want that to be true over time. Preferences can change! * We are a small company and we want to remain this size for as long as possible, therefore every Doister has an impact on our goals and results. It is therefore vital that our leadership team is still making direct contributions to our squad work and day to day deliverables. * An individual contributor (IC) can have the same impact and leverage as a people manager in creative fields. For example, most of the world-changing work that Jony Ive did at Apple was as an IC and not a manager (he designed many core products). * We have seen that hands-on leadership results in fantastic outcomes at even large companies (e.g., Stripe is one of the other companies with this leadership philosophy). * Various studies also confirm that employees are far happier when people lead them with deep expertise ([HBS Article](hbr.org/2016/12/if-you…)). The hands-on management mantra also aligns with our core values: * Mastery, because you can't master something without continuous hands-on work. * Independence, because we want to have Doisters manage their work with little or no direction. Some implications of this philosophy include: * We are all hands-on and directly responsible for deliverables. * We always hire functional experts, even for leadership positions. * We optimize our structures and workflows to prioritize this, e.g., small teams and few direct reports for leaders. IC work is any work that an IC could do; some examples: * If there's a thread from a teammate (e.g., discussing a technical plan for their DO) and everyone's chiming in and writing a reply, it's hands-on work; when you write the monthly update, it's not. * When reviewing PRs as part of random review roulette, it's hands-on work. * When reviewing PRs for mastery track notes, it's not.
English
3
0
19
2.8K
@jason
@jason@Jason·
We started an AI founder twitter group... reply with "I'm in" if you're a founder and want to be added
English
10.8K
134
4.6K
904.2K
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
@amix3k I think it is very important to make sure that we do not outsource our thinking so that we can make sure we maintain and build: taste, judgment and trust.
English
0
0
0
105
Amir Salihefendić
Amir Salihefendić@amix3k·
We will work less and have a lot more. For most of human history, people worked longer, harder, and under much harsher conditions than we do today. Every major technological revolution reduced drudgery, increased productivity, and enabled more people to enter higher-quality work and a better life. The transitions were messy, but the long-term impact was better jobs. AI and robotics will do the same. People are also not going anywhere. We will still want people accountable for outcomes. We will still value people who can exercise judgment, build trust, have taste, and decide what matters. Less grunt work. More leverage. More abundance. That’s why I’m optimistic about the future! 😊 I feel like this is critical to share as there’s so much pessimism going around. We can build an amazing future.
English
9
2
38
3.9K
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
Success with AI will not come from simply picking the best model. It will come from building the best workflow around the model. Day 2 had a lot of great talks, but the common thread was clear: AI coding is becoming a systems problem, not just a model problem.
English
0
0
0
11
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
Our products now need to work for agents too. That means: - APIs - auth - docs - CLIs - interfaces All need to become more agent-friendly. In many cases, your next user may not be a person clicking a dashboard.
English
1
0
0
14
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
Day 2 at @AIEMiami left me with one big takeaway: AI coding is no longer just about model quality. We’re moving from “LLMs that help write code” to “agent-driven software systems”.
English
1
0
0
25
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
Summary of Day 1: Agents scale execution. They do not scale judgment. Which means the winning teams will be the ones that rebuild structure on purpose: pipelines, guardrails, review, persistence, and restraint.
English
0
0
0
11
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
The product lesson was maybe the most important: AI removed the engineering friction that used to kill bad ideas early. Teams can ship bad ideas much faster. Execution scaled. Judgment didn’t.
English
1
0
0
10
Dragoș Mușetescu
Dragoș Mușetescu@dragosdm·
@aiDotEngineer Miami Day 1 had one clear message: The future of agents is boundaries, not authority. Best ideas I heard: - code > tool calls - pipelines > mega-prompts - skills/markdown > bloated abstractions - agents should author artifacts, not touch prod - secrets should never reach the model Agents scale execution. They do not scale judgment. That’s now our job.
English
1
0
1
22