Загрузка видео...

Не удалось загрузить видео

На главную

Engineering through destruction! 🔨 Dyson's testing philosophy: break it until it fails, then rebuild it better. Here's what that actually means in practice: vacuum batteries go through 1,200 charge/discharge cycles, the Supersonic hair dryer cable gets wrapped and unwrapped 7,800 times, Corrale straightener plates open and close 400,000 times,...

279,857 просмотров • 4 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

James Dyson’s advice for founders: “You have to enjoy failure” “If you are exploring new territory, experimenting, and trying to do something different, you’re going to fail many times and you’ve got to bounce back from it,” James Dyson explains. The billionaire inventor argues that you should actually learn to enjoy failure: “Failure is so much more interesting than success — the reason something goes wrong is often very interesting whereas if works you just say ‘great that works’ and don’t even stop to wonder why it works. You’ve got to learn to enjoy failure. That sounds like a difficult thing to do, but you have to enjoy failure if you want to improve things.” He continues: “It always saddens me that school doesn’t really teach that. At school or university, the thing is to be brilliant and get the answer right the first time. There are brilliant people who can do that, but for the rest of us, we’re not brilliant and to get there we have to strive and go through failure. You don’t get it right the first time. You don’t get it right the second time. In my case, and I counted it, it was 5,127 times . . . That sounds like struggle and it was a struggle, but it was a hugely enjoyable struggle. The debt was mounting, and I had three children, a wife, a home, and a mortgage to pay like everybody else, but I had a real aim in life and I had to get there. And the failures were interesting because I learned from almost every single one of them.” James Dyson concludes his autobiography by saying: "Listen, it's easy for me to celebrate my doggedness now. I made $300 million last year, but I'd be lying to you if there weren't times where I went inside my house, had my wife look at me like I'm a failure, and cry myself to sleep. I got up and did it again anyway because excellence is the capacity to take pain.” Video source: David Senra (2025)

Startup Archive

14,401 просмотров • 4 месяцев назад

John Ternus, Apple's SVP of Hardware Engineering, explains why Apple deliberately made the iPhone harder to repair, and why the math says it was worth it: In a conversation with MKBHD, John frames the design challenge by asking you to imagine two extremes: "Sometimes for me I find it helpful to kind of think about the book ends. Like if you imagine a product that never fails, right? That just doesn't fail. And on the other end, a product that maybe isn't very reliable but is super easy to repair." His position is clear: "Product that never fails is obviously better for the customer. It's better for the environment." When pushed on whether infinite repairability and infinite durability have to be mutually exclusive, John acknowledges they aren't always, but explains why the tension is real, using the iPhone battery as an example. Batteries wear out. If you want to extend the life of the product, they need to be replaced. But in the early days of iPhone, one of the most common failures wasn't the battery, it was water: "Where you drop it in the pool or you, you know, spill your drink on it and the unit fails. And so, we've been making strides over all those years to get better and better and better in terms of minimizing those failures." That work led Apple to an IP68 rating, the point where customers fish their phones out of lakes after two weeks and find them still working. But there was a cost to achieving that level of durability: "To get the product there, you've got to design a lot of seals, adhesives, other things to make it perform that way, which makes it a little harder to do that battery repair." That's the deliberate tradeoff. Apple chose tighter seals and stronger adhesives, knowing it would make battery replacement more difficult, because the reliability gains were worth it. John argues the math backs this decision: "It's objectively better for the customer to have that reliability and it's ultimately better for the planet because the failure rates since we got to that point have just dropped. It's plummeted, right? The number of repairs that need to happen and every time you're doing a repair, you're bringing in new materials to replace whatever broke." His conclusion reframes the entire repairability debate: "You can actually do the math and figure out there's a threshold at which if I can make it this durable, then it's better to have it a little bit harder to repair because it's going to net out."

Big Brain Business

384,726 просмотров • 1 месяц назад

From Eric Vishria on how the top AI founders are building products completely opposite of the SaaS era: "One of the things that is really different in the AI world versus the SaaS world, is that in the SaaS world, over and over again, you had people who really understood the customer. And the problem. And then they understood a domain. They understood what the technology was more or less capable of. But it wasn't a real question of if you could build something or not. For example, take Salesforce, Workday, and ServiceNow. CRM existed before Salesforce. HR management existed before Workday. Same thing with ServiceNow. So in every case, Salesforce followed Siebel. Workday followed Peoplesoft. ServiceNow followed Peregrine and Remedy, and others. So they were just kind of, cloud SaaS versions of the prior generation product. They just understood the customers. They understood the problem. And they were just like, here's a better version. And that evolved a little bit over time in SaaS land. But that's what it is. And so product development in that way was done by people who really understood the customer and the problems. And then just took advantage of the next wave. And this is almost diametrically opposite of product development in the AI era. When I look at the teams that are having the most success today, they have intimate knowledge of the models. They are right on the frontier of understanding which models are better at what, and why, and when. And what they're going to be good at and what they're not going to be good at. And what they're spending their time on, is figuring out how do I apply this capability of this model to this domain or to this user. So they're actually working inside out or technology out, versus customer problem in. And of course, they understand the customer problem. And a lot of times they have firsthand knowledge of it. But they're really close to the metal and capability, and they're applying it. And I think this is a really different way to develop products than in SaaS. I started my career as a product manager a long time ago, and it's almost the complete opposite of everything you learned. "Listen to the customer, understand it, then bring it back to the engineering and product teams." If you did that right now, ask a bunch of customers what they want out of AI, and you brought it back, for the most part, it may not be possible today with today's technology. Whereas the teams that are winning right now really understand the technology and are applying it out. And so I think this reversal matters. I think it's a big difference in terms of how companies are getting built. And maybe even the types of entrepreneurs that will be successful. I'm not sure. You're seeing some real change there. Look at the Bret Taylor's at Sierra. That's a super, super technical founder who really gets it. Brett and Clay really get it. You look at Michael and his co-founders at Cursor. They're super technical founders and they get it. They all really understand what these things can and can't do. And that's a pretty different dynamic relative to the way the best SaaS companies got built." Link in bio for the full conversation going deep on the current class of startups going from zero to $100m+ in ARR within 12 months.

The Peel

209,320 просмотров • 1 год назад

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

191,430 просмотров • 1 месяц назад

Rich Roll on why waiting to "feel like it" is a trap: "You can't think your way into the mood that you seek or the state of mind that you aspire to inhabit. Action is the only thing that can trigger that change." Rich uses running as the perfect illustration of this principle. Imagine you wake up in the morning and you're supposed to do a run because you're training for a race. You don't feel like it. So what do most of us do? "We all resort to that state where we think, 'Well, I don't want to do it right now. I'll just wait until I feel like doing it and then I'll do it then.'" But here's the problem with that logic: "If you're waiting until you feel like doing something, chances are you're probably never going to get to it." The mood you're hoping will arrive on its own? It's not coming. Not without action first. "To take the action despite how you feel about it is the thing that catalyzes the state change." You don't run because you feel motivated. You feel motivated because you ran. He points to what every runner knows from experience: "When they finish the run, they're always glad that they did it. They don't generally regret it. And then they feel better." Notice the sequence. The good feeling comes after the action, not before it. The state change is the reward for showing up, not the prerequisite. And this isn't just about running. As Rich puts it: "That example is applicable to all areas of life." The workout you're avoiding. The conversation you're delaying. The project you're putting off until you're "in the right headspace." You're waiting for a feeling that only exists on the other side of doing the thing.

Kevin Tanaka

10,256 просмотров • 1 месяц назад

Bill O’Reilly and Chris Cuomo just got into a HEATED sparring match over where the “weapons of mass destruction” narrative in Iraq actually came from. O’Reilly said it started with the New York Times — Cuomo bet him $100K that it did not. O’REILLY: “I was wrong about weapons of mass destruction in Iraq. And the reason I was wrong was because Saddam Hussein told his own generals he had them.” “And then those generals leaked it to the New York Times and put it on page one. And I bought it!” CUOMO: “Well, that’s not what happened. That’s not what happened.” “The Bush administration lied about there being yellow cake uranium and there being weapons of mass destruction and that’s how it started.” “I didn’t come through the New York Times, it came through the Bush administration.” O’REILLY: “If you go back, and this is easy for you to do, it was page ONE of the New York Times...” “Don’t say it isn’t true! Because every word I said is TRUE.” CUOMO: [Laughs] “Well...you think every word you say is true and that’s okay.” O’REILLY: “No! I can prove it!” “Cuomo, you want to put 10 grand on it now? I’ll prove it.” CUOMO: “Yes. I’ll tell you what, I’ll put $100,000 on this proposition, that the idea that Iraq had weapons of mass destruction did not start with the New York Times.” “It started with the Bush administration and that’s why Colin Powell wound up losing his career, when he very well could have been a superior president of the United States because they made it up, they ruined intelligence careers and they lied.”

Overton

393,831 просмотров • 15 дней назад