22 Jul 2016
Reading time ~1 minute
What I Did
- Weekly Intern Group Meeting
- Taught a Bengali Song to Laura, Becky, Michael, and Albert
- Further refactoring of CK components for “These Numbers Matter”
What I Learned
- Child components should provide the dynamic data for a parent’s onChange method to then use to update its props, rather than leaving said updating to be declared in the child component. It’s best to avoid sending too much responsibility for state management for a parent into a child. This makes it easier to reuse components, and easier to reason about how change management occurs. However, without such passing of props, blocks that manage a lot of properties can be cumbersome.
- It’s generally good practice to using mixins that obfuscate form change for React components.
- It’s a good idea to relegate the rendering of a component’s label to the component itself opposed to clumsily defining those labels externally.
What I Still Don’t Understand
It seems that I’m still shaky on best practices with regards to committing, branching, merging, pulling, rebasing, pushing, and all that jazz. I feel that I’m always second guessing myself on the more weighty commands. I’ve got to take some serious time to understand the ins and outs of revision control. Luckily, nothing tragic has happened just yet.