Tyler McGinnis - Medium

[...] we do, we would pass that data to the child component as an attribute. In this example, we pass the UserImage component all of the images that the [...]

[...] parent. The parent component is rendered to #app (in App.js), which then renders the child component passing in “child” as a property on props. Now comes the fun part. Let’s head over to [...]

[...] ” component. The way this parent/child relationship works is our UserInfo component, or the parent component, is where the ‘state’ of the data for both itself and the UserImage component (child [...]

[...] code. Notice all we’re doing is creating two components, one child, one parent. The parent component is rendered to #app (in App.js), which then renders the child component passing in “child” [...]

[...] . It’s also something I’ll most likely keep working on even after I graduate Hack Reactor since it’s a project that never really has an end. Hopefully it will be deployed by this [...]

[...] of the members of the Senior class and got a pretty good overall feel for how it is to be at Hack Reactor. Here’s the link to check out.   Tech Crunch visits Hack Reactor   Tyler [...]

[...] Last week ended with me slightly worried. Although I got through the last two sprints here at Hack Reactor, I didn’t feel very confident in them. The hard part about being in such an intensive [...]

[...] Another fantastic week has passed here at Hack Reactor. At this point all of the sprints and the lectures are kind of blending into one and I have no [...]

[...] in an efficient manner. Next we’ll talk about persisting our data with Firebase and using React Router for, you guessed it, introducing routing into our app. After that, we’ll put it all together [...]

[...] Combining React.js, Flux, React Router, Firebase, Gulp, and Browserify. (Coming Soon) Building React Applications with Gulp and [...]

[...] ; into our controller. Now let’s add some ‘private’ variables to our callback function. These won’t be directly accessible from the controller, but we will eventually [...]

[...] what we’re doing above. We create a gulp task called transform and pass it a callback function. In our callback function we grab the path.JS array. Gulp then gets each one of [...]

[...] this code might look a little wonky. All map does is it creates a new array, calls our callback function on each item in the array, and fills the new array with the result of calling the [...]

[...] Soon) Pt III: Architecting React.js Apps with Flux. (Coming Soon) Pt IV: Add Routing to your React App with React Router. (Coming Soon) Pt V: Add Data Persistence to your React App with Firebase. ( [...]

[...] . Pt III: Architecting React.js Apps with Flux. (Coming Soon) Pt IV: Add Routing to your React App with React Router. (Coming Soon) Pt V: Add Data Persistence to your React App with Firebase. ( [...]

[...] we would like our HTML Template to look like. React.render – Renders a React component to a DOM node. state – The internal data store (object) of a component. [...]

[...] browser. This is fantastic for React because as you’ve probably guessed by now, each React component we create can be it’s own module that we can then require in other components based off [...]

[...] them, which is another testament to how great Hack Reactor is.   Until next week,   Tyler McGinnis, who has been slacking on posting technical blog posts. My bad.   ps. BYU dominated [...]

[...] athlete who experiences the same void I did should consider following the path I took.   Tyler McGinnis [...]

[...] have a more extensive post on finishing Hack Reactor and why I chose to drop out of college. Tyler McGinnis [...]

[...] and I definitely am inspired by all of the support I have received from you all.   Tyler McGinnis ps I’m hopefully going to have two/three more technical blog posts up by next Sunday. [...]

[...] , and one day probably will, write a whole blog post on overcoming mental barriers in Software Engineering. The secret? Well, you kind of just have to trust what you know and understand you& [...]

[...] those people who didn’t care about pulling a profit. That’s what I love about Software Engineering. I find pure joy and satisfaction from creating an app that those developers I look up to [...]

[...] learned. After about Tuesday I realized that I do know a whole lot about Javascript and Software Engineering in general, it just took letting me go on my own to find that out. I now know why the [...]

[...] of HTML, CSS, JS, and some internal data specific to that component. I like to think of React components as the Kolaches of the web. They have everything you need, wrapped in a delicious composable [...]

[...] access to all of NPMs packages, but we’re now able to require only the packages (or React components) we need to for that specific file. This solves our problem of all of our components [...]