My goals were to: (1) master the foundations of Ruby and object-oriented programming, so that I could (2) look at a problem and have conceptual intuition about the algorithm required without needing to go straight to my computer. At a non-technical level, I sought to both ask for and provide support frequently in order to create a healthy learning environment.
- A: End-of-Module Assessment: X
- B: Individual Work & Projects: X
- C: Group Work & Projects: X
- D: Professional Skills: X
- E: Feedback & Community Participation: X
(Notes & scores from your assessment rubric)
Below are the projects I worked on independently to develop mastery of OOP and the Ruby lanuage. They are listed in chronological order.
Date Night is an application that constructs and traverses a binary search tree. Given attributes of the tree, such as depth or node value, the program traverses the tree via recursion to implement a given method, such as determining the number of "child" nodes that belong to a "parent" node.
Assessed By: Jeff Casimir
Evaluation Notes
- 34 tests, all pass
- Testing looks good at multiple levels
- Implementation is strong with some little bit for refactoring
Score
-
Test-Driven Development
3: Application is well tested but does not balance isolation and integration tests, using only the data necessary to test the functionality
-
Functional Expectations
4: did two extensions
-
Breaking Logic into Components
3: Application consistently breaks concepts into classes which encapsulate functionality. (SRP).
-
Fundamental Ruby & Style
3: Application shows some effort toward organization but still has 6 or fewer long methods (> 8 lines) needs some refactoring, and is mostly idiomatic.
The following projects involved at least one other partner, and are listed in chronological order.
- GitHub URL
- DTR Memo
- Original Assignment Complete Me extends the idea of binary search tree nodes to the concept of Tries, in which a node has N number of branches instead of just two. The program stores words via connected node paths, where nodes store hash links with the next letter as the key and the next node as the value. This type of data structure is most useful for predictive text features in an application. More specifically, as a user types, all of the pathways from the most recent character in a string are populated (displaying only the first few or most popular) and offered as suggestions so as to save the user from extra typing.
Assessed By: Sally MacNicholas
Evaluation Notes
- Overall great job
- Room for improvement to break out if/else statements into separate methods
- Discussed methods that are doing one thing OR another. Could break those out into its own for SRP
- Good job testing for edge cases
- Did the address extension
Scores
-
Test-Driven Development
4: Application is broken into components which are well tested in both isolation and integration using appropriate data, including edge cases
-
Encapsulation / Breaking Logic into Components
3.5: Application consistently breaks concepts into classes and methods which have appropriate scope and responsibilities (SRP).
-
Fundamental Ruby & Style
3.5: Application shows some effort toward organization but still has 6 or fewer long methods (> 8 lines) needs some refactoring, and is mostly idiomatic.
-
Enumerable & Collections
4: Application consistently makes use of the best-choice Enumerable methods and collections
-
Functional Expectations
4: Application fulfills all base expectations and one extension
(feedback to me)
(description)
(evaluation comments)
(evaluation scores)
(feedback to me)
(Intro)
Voting is an interesting topic. As someone brought up in our discussion, it's hard to imagine anyone who is expressedly "anti-voting", so on the other side of fervent "Vote or Die"-type mantras are are not fists or counter-arguments, just lazy shoulder shrugs. Moving forward, the dialectic of rights and responsibilities is top of mind. It seems like current US culture teaches us to cling to the former, and barely touch the latter, so I want to make a better effort to keep in mind the responsibilities I have that enable my rights.
(3-4 sentences summarizing your takeaways from each session, including things you're continuing to think about, things you learned, things you're doing differently)
It's hard to accept that relatively static representations of a person can be so influential in impression management, but that's the case. I used to roll my eyes at this kind of stuff, but now I better understand the idea of "perception is reality," and I have newfound intrinsic motivation to develop a quality personal brand online (and off).
- Workshop URL
- DTR Memo: See Complete Me
Opening up a deep conversation about personal habits and life situations with a relative stranger isn't the most natural thing in the world, but that awkwardness is worth it. Most, if not all, collaborations will have some turbulence, so might as well frontload it to clear space for quality work time. I look forward to learning more about myself through these in order to better DTR.
- Workshop URL
- See feedback from and for me in the Complete Me project section.
Historically, I have the hardest time receiving feedback from the people to whom I feel closest. I enjoyed learning about the relationship trigger, and how to put it in perspective to ultimately move past it. Moving forward, I will work on moving from a "you or me" story to a "you and me" one, where the snag is located in the relationship system instead of at the individual level.
(takeaways from session)
(feedback from me)
(feedback to me)
Kids Who Code
- 10/15/16: Vector vs. Bitmap animations and setting cloud variables on Scratch.
- Helped kiddos navigate the Scratch interface and set a high score cloud variable.
( Leave blanks for reviewers )
( Leave blanks for reviewers )