@metapreston I love this clip, it's a great answer to the otherwise nebulous question of 'how good should our product be'. Most leaders don't have any coherent answer to that question, let alone a good one. Wrote about it last year: https://t.co/s0NOBCMPpR
Teams building closed-source software benefit from working in a high-coordination, high-obligation environment. They can plan, delegate, and execute tasks efficiently by relying on the structure and continuity provided by their organization. What software engineering practices will make such a team as effective as possible? And how do those practices differ from the ones used in open-source software? https://t.co/mDXEjVoIEZ
"We risk falling into what I will call the “McNamara fallacy.” I’d like to state what this fallacy is, why it has suddenly become a major threat, and how it might be avoided." - Daniel Yankelovich, "The New Odds" (1971) https://t.co/qPWM84ZxXt
"In most cases, closed-source development is optimized with a combination of small PRs, fast code reviews, and automated testing. These three practices form a reciprocal frame; they are mutually-supporting and reinforcing."
Daniel Yankelovich coined the term ‘McNamara fallacy’ on October 15, 1971 during a speech titled ‘The New Odds’ at the eleventh annual Marketing Strategy Conference of the Sales Executives Club of New York https://t.co/qM7C3vcqCU