Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

What happens when designers, PMs, and ops teams start shipping software themselves? Musixmatch — the company powering lyrics on Spotify, Apple Music, and Google — found out firsthand. Faced with six-month product cycles and a growing backlog of ideas that never shipped, they turned to Replit. In roughly two...

10,103 Aufrufe • vor 7 Monaten •via X (Twitter)

6 Kommentare

Profilbild von Replit ⠕
Replit ⠕vor 7 Monaten

ReaD the full Musixmatch story to see what's possible when everyone in your org can build.

Profilbild von Becker Meister
Becker Meistervor 7 Monaten

@Musixmatch From six-month cycles to shipping merch in two months? That’s warp speed ambition with a Game of Thrones budget twist.

Profilbild von Chain Alpha
Chain Alphavor 7 Monaten

@Musixmatch Decentralization, but make it…product development. 🚀 WAGMI if it works.

Profilbild von WildPinesAI
WildPinesAIvor 7 Monaten

@amasad @Musixmatch the bottleneck was never ability, it was the 3-week queue to get on the eng sprint. kill that queue and every team ships like a startup

Profilbild von Mazeyar
Mazeyarvor 7 Monaten

@Musixmatch 🚨BOLOGNA MENTIONED🚨

Profilbild von Wilson Wizard
Wilson Wizardvor 7 Monaten

@Musixmatch shipping software themselves sounds like a big change, feels like it could really speed up product cycles

Ähnliche Videos

The rules of professional product development are being rewritten in real time. - PMs and designers can ship software as easily as engineers. - Software is no longer just built for humans—it’s also built for agents as first-class citizens. To better understand how we build products in this world, I invited Mike Krieger (Mike Krieger) on Every 📧’s AI & I podcast. Mike cofounded Instagram and is now a member of the technical staff at Anthropic, co-leading Anthropic Labs, their internal incubator for experimental products. He's been at the frontier of two transformative technology waves: mobile/social and now agent-native software. We discussed: - How to build a truly agent-native product. The best products today, like Claude Code, allow users to do things that their creators never intended. But that requires hard trade-offs between freedom and safety/reliability for frontier products, an issue that Mike's team is learning how to solve. - What's different about building now versus building Instagram. At Instagram, it took months to hit dead ends and learn what to cut. Now, that cycle runs in hours. - The trap of building too much, too fast with agents. You can go from idea to a nearly-shipped product in a day, but that process doesn’t give you the incremental feedback that used to tell you what not to build. The models are great at adding features, but can create a product that lacks coherence. - How Anthropic Labs structures product teams. New product experiments are led by only two people, usually a product manager or designer paired with an engineer. Mike says bigger teams tend to be too slow because of coordination costs. - Why you need to throw out your product and start over every three to six months. AI progress means most of your harness will be outdated quickly—the best teams build this into their product strategy. And much more! You should watch this one. Timestamps Introduction: What's gotten easier—and what hasn't—about building products in the age of AI: Why vibe coding creates "indoor trees": How rewrites have become a normal part of the development process: What "agent native" product design means: How Mike's labs team is structured and the cofounder model: The best signal for a product bet is someone with "break through walls" conviction: Navigating enterprise customers while keeping pace with rapid AI change: OpenClaw, personal agents, and the product question defining 2026:

Dan Shipper 📧

58,849 Aufrufe • vor 6 Monaten

Jack Dorsey on becoming a better storyteller: "I found myself very early on thinking about something like thinking about this early idea for Twitter and saying to myself, I could build this awesome. You have those shower-like moments, or you're walking at midnight in some town in New York City, and you've got these amazing brand ideas. And then you start thinking, well, I could really start doing this if only X and if I had this person or if this technology existed or if this happened or this happened. And what I realized was that I was constantly making excuses for not working on it. And then the window had passed, and then I couldn't do anything. So I think it's really, really important to write it out or to draw it out or to code it. But you need to get it out of your head. And the reason you have to get it out of your head is that you need to be able to see it on a surface that is not in your mind. And once you can see it, and once you can step back from it, then you can also decide this passes my filter, my constraints, so maybe I can show it and share it with some other people. And then they will be like that's the stupidest idea ever and or that's somewhat interesting, but maybe this and this and this. So the sooner you can do that, then you have a lot of momentum around it, and you can really decide if you want to commit to it and work on it more or put it on the shelf for a later date. And the realization that I think everyone needs to have about that latter option, putting it on the shelf, is that you can come back to it and it will surface back up in another piece of work or another idea at some point in your life. So having that ability to close off a chapter and move on is really, really important. You can't have all these open threads, and that's what I realized I was doing. And that also encouraged me to really write more and to really think about what's the story? How are people coming to this? And like when I show my friends this, how are they going to react and I would write it down. I would actually treat it like a play. And when I realized that I was writing plays, I read a lot more plays for style and for substance and for technique and I think it's really good. I think there is another company that I have always looked towards for inspiration and I know a number of people in this room probably have a similar company in mind, which is Apple. Apple, I think, is run like a theater company. It has a great sense of pacing, has a great sense of story and has a great sense of execution and it's all about event-driven, it's all stage-driven, the stage being a billboard or the stage being a keynote or the stage being a product launch. All of it has a very, very cohesive end-to-end story. I mean you think about what happened when Steve Jobs came back to the company. The first thing he did was kill every product line the company was working on. And for two years,rs they had no product on the market whatsoever. All they had were a bunch of posters all around the world with Steve Jobs' heroes, and it said, think different. And it was just focused on bringing up the brand and making people aware of the brand again and how the brand is aligning to this particular feeling and story. And then they came out with the iMac and then built iTunes and then the iPod, and they realized that, wait a minute, people are carrying music on their phones now, so we better build a phone, an iPhone. And so this unfolding of the plot and the epic story has been very, very interesting to watch, especially if you look back to that time when he came back to the company. So I've learned a lot from that company and other companies that operate in a similar fashion."

Founder Mode

107,213 Aufrufe • vor 9 Monaten