Reusable Components

Web developers are building applications based on collections of reusable components, but how do you assemble those collections? When do you spend the time to make a thing reusable? Presentation includes a case study of two Chartbeat components, and some general guidelines for thinking about reusability.

To see a transcript of the talk, click the gear icon and open speaker notes: https://docs.google.com/presentation/d/1uaJgFERVuW1u9dOtT_xzx6iVdKqYRDnZYpiGXm3_9uA/pub?start=false&loop=false&delayms=3000

Transcript

1. Reusable Components
5. 1. It’s Slower and Tougher
6. 2. You Don’t Know The Future
7. 3. But, Customization!
8. Case Study: 2 Examples
9. The Good
10. vs. Component re- implemented 3 times REUSABLE NOT REUSABLE cost to implement from scratch cost to convert and maintain reusable component cbTooltip
11. TOOLTIP!
13. The Bad
15. vs. Component re- implemented 3 times REUSABLE NOT REUSABLE cost to implement from scratch cost to convert and maintain reusable component horizontalBarChart Custom stuff added/fixed later Initial work to make reusable
16. The Ugly
18. • Arbitrary number of columns from different property values • Relative bar width based on a property value • Sorting based on a property value. • Optional column headers w/ icon directives • Ability to remove bars • Custom data filters per column Shared / Expected Functionality Custom / Unexpected Functionality
19. But what does it all mean?
20. 1. Think before you reuse. 2. Respect your elder (components). 3. Beware attribute hell.
21. Questions/Complaints/Stock Tips: @dbow1234