Abstraction @ Kalo

An abstract talk on the topic of abstraction. How meta.

This explores how to measure and consider abstraction across everything.

Transcript

1. Abstraction
2. On the Spectrum of Abstraction Cheng Lou @ React Europe 2016
4. Abstraction (powerful ↑)
5. Product (useful) Abstraction (powerful ↑)
6. Cost Product (useful) 1 2 3 2 3 Abstraction (powerful ↑)
7. Cost Product (useful) 1 2 3 2 3 What level of abstraction do 
 we need to cover our product? Abstraction (powerful ↑)
8. Cost Product (useful) 1 2 3 2 3 What level of abstraction do 
 we need to cover our product? Really Abstract. Abstraction (powerful ↑)
9. Cost Product (useful) 1 2 3 2 3 What level of abstraction do 
 we need to cover our product? No Abstraction. Abstraction (powerful ↑)
10. Cost Product (useful) 1 2 3 2 3 What level of abstraction do 
 we need to cover our product? Mid Abstraction. Abstraction (powerful ↑)
11. Why wouldn’t you always want all the power?
12. Why not write everything with 1’s and 0’s?
13. Constraining provides properties Abstracting loses context
14. Right. What does this mean?!
15. Everything I just spewed is here.
16. What would be more useful are these. Examples!
17. Example #1: Kalo Invoices
18. Example #1: Kalo Invoices :( Undesired product
19. :( Example #1: Kalo Invoices
20. Example #2: Documentation
22. Example #2: Documentation
23. Example #2: Documentation
24. Example #3: DRY
25. Example #3: DRY
26. Example #3: DRY Cost
27. Example #3: DRY Cost
28. Example #4: The Frontend
29. Example #4: The Frontend
30. Example #4: The Frontend
31. Example #5: PaaS / Dennis
32. Example #5: PaaS / Dennis
33. Example #5: PaaS / Dennis
34. To conclude…
35. Abstraction is a constant battle between cost, properties and product.
36. Questions?