src
└─ app
└─ alongwindedfolder
└─ stuff.jsx
└─ stuff.cscc
└─ theotherfolder/
└─ otherstuff.jsx
└─ otehrstuff.scss
import Stuff from './realShort/stuff.jsx' |
render() { | |
return( | |
<Transition> | |
<Hello /> | |
</Transition> | |
) | |
} |
import React, { Component } from 'react'; | |
import PropTypes from 'prop-types'; | |
import shortid from 'shortid'; | |
import styles from './transition.mod.scss' | |
export default class Transition extends Component { | |
id = 'transition' + '-' + shortid.generate(); | |
property = this.props.transProperty; |
Introduce the project: I worked on Rails Girls Summer of Code site, which is a program that awards scholarships to woman to work on open source projects. The website is built on Jekyll, a static blogging gem that can be served on github pages.
What was it like jumping into that codebase? Per usual, jumping into the code base was a little frustrating. Having never used Jekyll the structure was a bit weird, and then tracking down where the issues we're pointing at took some digging around. Over all, though, this was a fairly straight forward setup. Download, bundle, and run Jekyll server.
What I did? I spent some time playing around with a styling issue, but abandoned that as I wasn't sure how it would be recieved. It also looked as if someone else was working on it, but that was unclear. I didn't want to start a conversation here as I figured my time could be spent elsewhere. At any rate, it was fun to dig around and try to find where the actual styles were hel
I've linked to my actual site, becuase while the blog posts are central to it, I'm also using the site itself as promotion. When I contant folks via cold outreach, apply for a job, or meetup with someone I can direct them to check it out. It's pretty simple for now, but the right people will appriciate how much work goes into getting something like this up and running.
I actually ended having 4 practive interviews. I'll be having my first actual interview this week...
My first interview session I was pretty nervious, for no reason really. I did ok at the 'soft' questions like, 'Tell me your story', did a little worse at the technical questions, and kind of struggled with the coding challaneges. By the 4th interview I had at least improved a little at each of these, especially the coding challanges.
Fork this gist and answer these questions to reflect on your learning experiences.
- What brought you to Turing?
- I came to turing to make a future for myself.
- Where do you see yourself after Turing?
- Working in the field. Struggling with a new job. Planning for the future.
- From concepts taught in class or your personal learning, what technical concepts do you enjoy exploring most?
- My favorite concepts to date are those that organize the stack, speed a user's experience, and those that have visual impact on the user.
- Environmental Issues and Outdoor Recreation
- Fine Woodworking Design and Building
- Interest in music and art
- Technology and computers
- Knowledge of conflict resolution and collaborative methods
- People with a good sense of humor.
- People with strong interests and hobbies.
- I believe that all strong relationships are based on the practice of empathy, and that relationships are the foundation of a happy life. Consciously connecting myself to others with emotional links has not come naturally, but is has certainly helped me be a better person.
- Empathy can help identify aspects of design that would otherwise have been overlooked. Putting yourself in the user’s shoes promotes exploration of ideas and fights convention.
- Why is driving on the right side of the road important for getting to your destination? Minimizing conflict in a collaborative setting is a key tenant of producing a good final product, no matter what you're aiming for. The lack of empathy isn't the spark in a grain silo; it's the failure to recognize, or indifference to, the situation becoming an out of control inferno.