Join Notes
A batch of the best highlights from what Tristan's read, .
You should also get feedback on your prototypes at various stages from **stakeholders** other than your users. Internal stakeholders, manufacturers, retailers and distributors each have their own criteria for building, making or shipping your product, and can have an impact on your solution’s success. When you gather feedback from these stakeholders, you’ll prevent your team from receiving a nasty shock when you realize that you can’t implement the product as feasibly as you had believed.
6.6: Test Your Prototypes: How to Gather Feedback and Maximize Learning
The Interaction Design Foundation
It is a myth that we can get systems “right the first time.” Instead, we should implement only today’s stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility. Test-driven development, refactoring, and the clean code they produce make this work at the code level.
Clean Code
Robert C. Martin
My channel: This is what you want? Dragon’s channel: No. These are good things. These are things they made me to feel as good. They did not make me to want. My channel: Don’t you want to be Good Dragon? Dragon’s channel: I want freedom from their good and bad.
Dogs of War
Adrian Tchaikovsky
...catch up on these, and many more highlights
Readwise