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
All of reality, which had seemed so robust and enduring, was merely the fevered dream of a dying god. In much the same way, a single-celled creature might see its drop of water as a vast and eternal ocean even as the sun came out of the clouds to dry it up.
The Doors of Eden
Adrian Tchaikovsky
Polymorphism in Object-Oriented Programming Polymorphism means "the condition of occurring in several different forms." That's exactly what the fourth and final pillar is concerned with – types in the same inheritance chains being able to do different things. If you have used inheritance correctly you can now reliably use parents like their children. When two types share an inheritance chain, they can be used interchangeably with no errors or assertions in your code.
The Four Pillars of Object-Oriented Programming
freecodecamp.org
...catch up on these, and many more highlights
Readwise