An abstract talk on the topic of abstraction. How meta.
This explores how to measure and consider abstraction across everything.
Abstraction
View Slide
On the Spectrum of AbstractionCheng Lou @ React Europe 2016
Abstraction (powerful ↑)
Product (useful)Abstraction (powerful ↑)
CostProduct (useful)1 2 32 3Abstraction (powerful ↑)
CostProduct (useful)1 2 32 3What level of abstraction do we need to cover our product?Abstraction (powerful ↑)
CostProduct (useful)1 2 32 3What level of abstraction do we need to cover our product?Really Abstract.Abstraction (powerful ↑)
CostProduct (useful)1 2 32 3What level of abstraction do we need to cover our product?No Abstraction.Abstraction (powerful ↑)
CostProduct (useful)1 2 32 3What level of abstraction do we need to cover our product?Mid Abstraction.Abstraction (powerful ↑)
Why wouldn’t you always want all the power?
Why not write everything with 1’s and 0’s?
ConstrainingprovidespropertiesAbstractinglosescontext
Right. What does this mean?!
Everything I just spewed is here.
What would be more useful are these.Examples!
Example #1: Kalo Invoices
Example #1: Kalo Invoices:( Undesired product
:(Example #1: Kalo Invoices
Example #2: Documentation
Example #3: DRY
Example #3: DRYCost
Example #4: The Frontend
Example #5: PaaS / Dennis
To conclude…
Abstraction is a constant battle betweencost, properties and product.
Questions?