I'm a leader. Resilient. Team-oriented.
Public speaking. Debate team in high school, president of groups in college, military officer chaplain, minister (sermons)
| Project: IdeaBox Group Project | |
| Group Member Names: Dustin LaDue, Leigh Larson, Derek Romero | |
| Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): | |
| Demonstrate comprehension and skill of CSS & HTML. Adhere to comp specs as closely as possible. Clean and tight iterations rather then quantity completion. Understanding of JS functionality of completed iterations. Seek PR / reviews from mentors for insight. DRY and refactored. | |
| Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
| Derek is cooperative, practical, maverick, courageous. Dustin is flexible / adaptable, cooperative, agreeable. Leigh is a maverick, pragmatic, approachable, flexible. |
| ###Description | |
| Over the Intermission break, I worked on CodeWars, kata 8, to practice pseudo-code skills, and gain exposure to different ways of coding. | |
| ####1. String Repeat | |
| Instructions: Write a function named repeatString that repeats the string (str), "n" times. | |
| Sample tests: | |
| ``` | |
| describe("Tests", function() { | |
| it ("Basic tests", function() { |
| Project: What's Cookin'? Pair Project Mod 2 | |
| Group Member Names: Horacio Borrego, Leigh Larson | |
| Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): | |
| Demonstrate comprehension and understanding of JS-- data manipulation and iterating over data. We are excited to build a program that is close to what we could design in the professional world. We will know we're successful if it works. | |
| Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
| Leigh is a maverick, pragmatic, approachable, flexible. Horacio is flexible, easy-going, and experienced in projects like this. |
| #### What is a "data model", and how does it relate to the DOM in a front-end application? | |
| Data model is your source of truth, it contains all raw data and its respective format. The data can be added or deleted, but it's pretty much the same, neutral data throughout the project. The DOM is how the data can be manipulated, accessed, by the crafted style application. This can be changed depending on the dev's needs / desires. | |
| #### What is a "framework?" And how does it differ from a "library?" | |
| A library is much smaller, less rules than a framework. We make the call to the library, whereas the framework calls our code. A good example would be jQuery vs Django. | |
| #### Why should we consider using a framework over vanilla JS like you have been doing in mods 1 and 2? | |
| We need to maintain that the UI is in sync with the state. It's not possible to implement efficient and complex UI with vanilla JS. | |
| #### What is a "component" in React? Why is it useful to have components? |
| Project: Rancid Tomatillos Project | |
| Group Member Names: Greyson Elkins, Leigh Larson | |
| Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): | |
| Demonstrate comprehension of React fundamentals and React router for multi-page user interface. Employ thorough testing and implement it early on the project. Complete project, aim for extension. Understanding of async/await. PR communication and small atomic commits. DRY and refactored. | |
| Team strengths & collaboration styles (consider discussing your Pairin qualities here): | |
| Leigh is pragmatic, approachable, flexible, hard work ethic. Independent but enjoys open communication. | |
| Greyson is detail-oriented, hard work-ethic, anti-procrastinator, experimental. |
This gist contains a short assignment I'd like everyone to complete before our formal lesson. The prework involves reading some of the React Router documentation, and will allow us to keep the lesson more hands on.
React Router is a library that allows us to make our single page React applications mimic the behavior of multipage apps. It provides the ability to use browser history, allowing users to navigate with forward / back buttons and bookmark links to specific views of the app. Most modern sites use some form of routing. React Router exposes this functionality through a series of components. Let's start by looking at the overall structure of an app using router:
| The number 47 has an interesting characteristic. | |
| If you take the number, plus its reverse (47 => 74) and then add them together to a number (47+74=121) the resulting sum is a palindrome | |
| Starting at 0, find the first 25 numbers that have this same characteristic as 47, but limit it to where the palindrome is greater than 1000. | |
| Collect the results in an array. Be sure that you're collecting the interesting numbers like 47, not the palindromic sums. | |
| Bonus points if you can do this without converting numbers to strings/arrays. |