></firebase-select> <firebase-select [options]=“itemsB” ></firebase-select> <firebase-select [options]=“itemsC” ></firebase-select> 1 2 3 Disclaimer: this is not the actual google component structure. This is just an example
System - Provider Abstractions Abstractions Abstractions Design System - Consumer Component Libraries Atomic Components - Across teams Base Style-guide Base Standards & Conventions Team Specific Basic Components Team Specific Style-guide Team Specific Standards & Conventions
to a new reusable component Simple Web Page Loop until code becomes incomprehensible ABC XYZ DEF QWS …. …. …. This creates a new abstraction. New design requirement, new variant added Universal abstraction now behaves differently for different cases.
to a new reusable component Simple Web Page Loop until code becomes incomprehensible ABC XYZ DEF QWS …. …. …. This creates a new abstraction. New design requirement, new variant added Universal abstraction now behaves differently for different cases. Sunk cost fallacy is whereby a person is reluctant to abandon a strategy or course of action even though the abandonment would be more beneficial - as you don’t want to lose out on the effort you have already sunk (can’t be recovered) Simple Web Page ABC XYZ DEF QWS …. …. ….
used together such that they share an implicit state that let’s them communicate with each other in the background. Parent Component Child Component 1 Child Component 2 Implicit state
elements in HTML. Apart they don’t do too much, but together they allow you to create the complete experience. — Kent C. Dodds <select name="cars" id="cars"> <option value="volvo">Volvo</option> <option value="saab">Saab</option> </select>