I just read a report about Eli Lilly’s “clock speed” approach. Basically, they break drug development into ~800 tiny decisions. Most fail, but the few that work get scaled big, and that’s how they keep producing blockbusters. It made me wonder why software doesn’t do the same. Instead of big roadmaps, why not run hundreds of small bets, kill the weak ones fast, double down on the strong ones. Software should be even easier to test than drugs, but in reality we keep building huge projects that flop. Has anyone here actually seen this approach used in dev teams or startups?
[link] [comments]


![[macOS] [Mac App Store - Game deals post #4 - DEATH STRANDING DIRECTOR'S CUT, Cyberpunk 2077: Ultimate, Frostpunk 2, The Medium, DREDGE and more at discounted prices.]](https://www.browardlocals.com/hello.gif)
![[iOS][Mac] Lifetime Pro IAP $10 → Free (48h) — RecordMark — voice notes with pins & transcription](https://external-preview.redd.it/YtBQSbs6xMBS__OIrr9eC4Ek71sFJIkh4c0So1yZWNc.png?width=640&crop=smart&auto=webp&s=0744d122255bc144037a76e5c4f087b72aa1cd1b)
![The Alabama Solution Trailer (2025) [1:57:00]](https://external-preview.redd.it/Djo00T_SWKRom0I3g_WiEUUbwfq9p7SdtGkTs_4kTak.jpeg?width=320&crop=smart&auto=webp&s=6cbbaea250ec8dd60e8a8db9f8e82ab1147b0172)


English (US) ·