Jen Woodson jenPlusPlus

Prework progress

Day 1

HTML is used to give web pages a structure, or layout, and to add extra meaning to the words on a webpage.
A tag is an instruction given to content on a webpage, enclosed in angle brackets (<>). The opening and closing tags let websites know where to begin and end each instruction. Each element is usually made up of an opening tag, the content, and the closing tag.
Attributes are used to give further meaning to the content of a webpage, such as color and font.
The head contains information about the webpage. The title contains the title of the page, shown in the browswer bar title or tab. The body contains information shown in the browswer window.
To view a page's source in Chrome, right-click the webpage, and choose View page source.
<title></title> is a title element, and it represents the title of the webpage. <b></b> is a bold element, and it bolds the text between the tags. <i></i> is an italics element, and it italicizes the text between the tag

Gear Up

Day 1

Empathy plays a great role in my life. It helps immensely in my marital relationship with my husband. We've been married 7 years now, and I know we couldn't have made it without empathy. Additionally, I try my best to treat the homeless as real human beings. I take the bus quite a bit, and I often interact with the homeless at bus stops. I try to lend a listening ear when I can.
Empathy helps you build better software by listening to the needs of the users. When you truly understand the users and their needs, you can create software to meet those needs.
Empathy is important in teamwork to understand your teammates and to reach the predefined goal. It's important to know your teammates' strengths and weaknesses in order to best delegate tasks to accomodate each team member's strengths, weakness, and abilities.
In my most recent job, my team was responsible for a presentation for a company-wide meeting. A team member of mine also had other responsibilities, including teaching two

Professional Development

29 Behaviors That Will Make You an Unstoppable Programmer

The 3 behaviors that resonated with me are Say "I don't know.", Take responsibility for your mistakes, and Always code review your own work first. These likely resonated with me because I have some experience with these behaviors.

I've had a little experience writing code in college and at my previous job, but I am a beginner. The few things I do know are far outweighed by the vast amount of things that I don't know. Whether in school or in a job after school, I'm going to get used to saying "I don't know" when that is the case. While this can be a very vulnerable phrase to utter, it's honest and will usually lead to finding out what you didn't know. That's a happy ending. Getting in over your head because you pretend to know something you don't will usually just lead to stress and anxiety.

I've made plenty of mistakes in my time on this Earth. Some of the mistakes I've owned up to, and others I've

Challenge Number // this is an h5 title in Markdown

Description of approach // this is a paragraph is Markdown [Challenge number](link to code pen here) // this is a link in Markdown.

Strengths & Storytelling Reflection

My strengths from StrengthsFinder are Restorative (likes to bring back to a state of "peace" or completion), Harmony (peacekeeper), Developer (encourager), Empathy (can understand how others feel), and Learner (continuing to take in information to better know a subject). I found this assessment to be very accurate. I really have a heart for people, and I really care about those around me. I've used these strengths daily at Turing. I make a conscious effort to encourage my classmates, relate with them when they share with me, and I'm learning new things everyday, which is very stimulating. I feel like I also have technical strengths that did not come up in my top 5. However, I think these soft skill strengths will help me with non-technical issues in order for my classmates and me to be successful. While I think I knew I had these strengths, I've been much more aware of them while at Turing.

I have struggled off and on at Turing. My biggest struggles come from mana

#Accessibility Commitments

I commit to actually consider accessibility when writing my applications. I haven't really considered accessibility since our Aria lesson in week one or two.
I commit to use semantic tags whenever possible and to add Aria attributes where semantics are not available/appropriate.
I commit to run my applications through AxE in order to understand how accessible they are and to make improvements in their accessibility.

	## Cold Outreach

	The mentor I contacted is Bekah Lundy.

	Date of contact
	08/15/2017

	Outcome
	We met for lunch on Tuesday, 8/22/17. We discussed networking and relationship building, her experience through Turing and beyond, and how I can be most job-ready by the time I leave Turing.

	Date of feedback conversation:
	8/25/17

	How did you prepare for the conversation?
	I thought about our Feedback lesson and how our project went.

	How did the conversation go for you? What was easy about the conversation? What was more difficult?
	This was a pretty easy conversation. I feel like Rufus and I have a lot in common, and therefore, we worked well together. Additionally, Rufus and I have developed a nice personal relationship. Since we knew each other a bit, it was easy to work together without a need for an 'introductory period'. We could just get down to brass tacks.

	What principles of feedback did you use in the conversation?

	What are you doing well as a pair programmer and collaborator?
	I like to think I am very encouraging. At the beginning of a pairing, I like to take a minute to appreciate the code that's already been written, and to celebrate what's already been learned. 'How did you get to this state?'

	How do you use your strengths as a team member?
	Many of my strengths have to do with soft skills, like empathy. I really try to build up my team members. We all have different strengths that will help us succeed!

	How would you like to continue to develop your strengths?
	I'd like the opportunity to continue working with different people. I also think the pairing program should go beyond Mod1/Mod2

	What would you like to improve on as a teammate?

	# Agile and Dev Strategies

	I think we're using a pretty Agile approach with our apps this mod. Since we have such a short time to complete them, we have to be adaptable. If the current path doesn't work, change it. It's almost as if we have day-long 'sprints'. At the end of the day, touch base with your partner. Either continue on the decided path or make a new path. Feedback from your partner needs to be pretty constant (at least daily), and feedback guides the development process. Ability to change at any moment has gone well. One thing that does not work well is adhering to a rigid schedule or plan. We must be flexible.