…leading the narrative enough that I don't get hung out to dry. Engineering predictability and its communication is the key to all success. Something that has helped me wildly has been the Microsoft book Software Requirements (3rd Ed) [0]. The system it lays out for planning, analysis, and risk mitigation is something everyone should read if they want to be more effective. It doesn't even have to be applied dogmatically. If…
……我手头唯一的一本是 Erika Hall 写的《Just Enough Research》。我还找到了 Joe Hair Jr. 等人写的《Essentials of Business Research Methods》。第二点：做用户想要的东西。这基本上属于软件需求的范畴，我推荐两本候选书：- Suzanne 和 James Robertson 合著的《Mastering the Requirements Process: Getting Requirements Right》；- Karl Wiegers 和 Joy Beatty 合著的《软件需求》（Software Requirements）。第三点：做点……
…the only book I have is Just Enough Research by Erika Hall. I also found Essentials of Business Research Methods by Joe Hair Jr. et al. 2. Build the thing that the user wants. That's mostly the real of Software Requirements and I have two candidates for you: - Mastering the Requirements Process: Getting Requirements Right by Suzanne and James Robertson - Software Requirements by Karl Wiegers and Joy Beatty. 3. Build something…
……不仅能让项目起死回生，还能用更少的时间超额交付，团队大家也更开心。另外补充：还要强烈推荐 Karl Wiegers 的《软件开发》（Software Development 第3版）[0] 以及它的配套书《软件需求视觉模型》（Visual Models for Software Requirements）[1]。把这些书里的知识，结合真正去学会探寻大家的兴趣和需求，不仅倾听他们在说什么，还要观察他们是否真正投入——这彻底改变了我的生活，我觉得我已经……
…to not only turn projects around but overdeliver in less time with happier people. EDIT: Also, shout out to Karl Wiegers Software Development 3rd Edition[0] and it's companion book Visual Models for Software Requirements[1]. Those books coupled with really learning to ask about peoples interests and needs and listen to not just what they are saying but watching to see if they are engaged changed my life and I think I've…
My top priority books: Software Requirements - Karl Wiegers Programming TypeScript - Boris Cherny Associate Cloud Engineer Study - Dan Sullivan Design Patterns - Gang of Four Refactoring - Kent Beck, Martin Fowler Programming…
…blocks and generate the visuals so you don't have to maintain/update two places. Any tool that does that? Also, integrating different level of complexity using system 1,2,3 (from https://www.amazon.ca/Software-Requirements-3rd-Karl-Wiegers...) to represent user flow diagram in addition to flow charts. Flow charts get confusing after some complexity. Useless if you want to represent multiple actors + messages. Systems/sub-systems…
……关于 Steve 的说法完全站不住脚，因为他描述的那些方法可不是什么稻草人靶子，而是绝大多数软件工程需求书籍中真实阐述的方法。你要是去看 Karl Wiegers 的那本《软件需求》（Software Requirements）——许多人都把它当成该领域的标杆参考书——里面描述的流程其实和 Yegge 喷的那套差不了多少。
…of Steve is way off base, because the methods he describes are not strawmen, but the actual methods described in most of the software engineering requirements books. If you look at Karl Wiegers book, Software Requirements, which is considered by many to be a leading reference on the subject, it describes a process much like the one Yegge criticizes.
……在叙事节奏上掌握足够的主动权，这样我就不会被晾在一边背锅。工程的可预测性以及相关沟通是所有成功的关键。对我帮助极大的是微软出的那本《软件需求》（Software Requirements 第3版）[0]。书中给出的规划、分析和风险缓解体系，任何想提升工作效率的人都应该读一读。甚至都不需要生搬硬套。如果……
…leading the narrative enough that I don't get hung out to dry. Engineering predictability and its communication is the key to all success. Something that has helped me wildly has been the Microsoft book Software Requirements (3rd Ed) [0]. The system it lays out for planning, analysis, and risk mitigation is something everyone should read if they want to be more effective. It doesn't even have to be applied dogmatically. If…
……我手头唯一的一本是 Erika Hall 写的《Just Enough Research》。我还找到了 Joe Hair Jr. 等人写的《Essentials of Business Research Methods》。第二点：做用户想要的东西。这基本上属于软件需求的范畴，我推荐两本候选书：- Suzanne 和 James Robertson 合著的《Mastering the Requirements Process: Getting Requirements Right》；- Karl Wiegers 和 Joy Beatty 合著的《软件需求》（Software Requirements）。第三点：做点……
…the only book I have is Just Enough Research by Erika Hall. I also found Essentials of Business Research Methods by Joe Hair Jr. et al. 2. Build the thing that the user wants. That's mostly the real of Software Requirements and I have two candidates for you: - Mastering the Requirements Process: Getting Requirements Right by Suzanne and James Robertson - Software Requirements by Karl Wiegers and Joy Beatty. 3. Build something…
……不仅能让项目起死回生，还能用更少的时间超额交付，团队大家也更开心。另外补充：还要强烈推荐 Karl Wiegers 的《软件开发》（Software Development 第3版）[0] 以及它的配套书《软件需求视觉模型》（Visual Models for Software Requirements）[1]。把这些书里的知识，结合真正去学会探寻大家的兴趣和需求，不仅倾听他们在说什么，还要观察他们是否真正投入——这彻底改变了我的生活，我觉得我已经……
…to not only turn projects around but overdeliver in less time with happier people. EDIT: Also, shout out to Karl Wiegers Software Development 3rd Edition[0] and it's companion book Visual Models for Software Requirements[1]. Those books coupled with really learning to ask about peoples interests and needs and listen to not just what they are saying but watching to see if they are engaged changed my life and I think I've…
我最优先要读的书目：Karl Wiegers 的《软件需求》（Software Requirements）、Boris Cherny 的《Programming TypeScript》、Dan Sullivan 的《Associate Cloud Engineer Study》、GoF 的《设计模式》（Design Patterns）、Kent Beck 和 Martin Fowler 的《重构》（Refactoring）、《Programming……
My top priority books: Software Requirements - Karl Wiegers Programming TypeScript - Boris Cherny Associate Cloud Engineer Study - Dan Sullivan Design Patterns - Gang of Four Refactoring - Kent Beck, Martin Fowler Programming…
……代码块并生成可视化图表，这样就不用在两处维护/更新了。有什么工具能做到这一点吗？另外，除了流程图之外，还可以参考（来自 https://www.amazon.ca/Software-Requirements-3rd-Karl-Wiegers... 的）System 1、2、3 来整合不同复杂度等级，用以表达用户流程图。一旦逻辑变复杂，流程图就会乱成一团。如果要表达多个参与者+消息传递，流程图根本没用。系统/子系统……
…blocks and generate the visuals so you don't have to maintain/update two places. Any tool that does that? Also, integrating different level of complexity using system 1,2,3 (from https://www.amazon.ca/Software-Requirements-3rd-Karl-Wiegers...) to represent user flow diagram in addition to flow charts. Flow charts get confusing after some complexity. Useless if you want to represent multiple actors + messages. Systems/sub-systems…
……关于 Steve 的说法完全站不住脚，因为他描述的那些方法可不是什么稻草人靶子，而是绝大多数软件工程需求书籍中真实阐述的方法。你要是去看 Karl Wiegers 的那本《软件需求》（Software Requirements）——许多人都把它当成该领域的标杆参考书——里面描述的流程其实和 Yegge 喷的那套差不了多少。
…of Steve is way off base, because the methods he describes are not strawmen, but the actual methods described in most of the software engineering requirements books. If you look at Karl Wiegers book, Software Requirements, which is considered by many to be a leading reference on the subject, it describes a process much like the one Yegge criticizes.