Jen Woodson jenPlusPlus

Jen Woodson - M4 Portfolio

Areas of Emphasis

I was really excited to learn about the backend using Node.

Rubric Scores

A: End-of-Module Assessment: X
B: Individual Work & Projects: X

Post-Grad Job Search Action Plan Template: Your first 30 Days

You are so close! You've spent the last 7 months working towards this -- graduation and finding your new dream job! This plan is meant to help you streamline your goals and get on the path to employment as a software developer during the first 30 days after graduation. Please fill out the plan by copying this template into a gist to submit in your portfolio.

As you fill out this plan, consider how your first job search will set the tone for your career trajectory in the software industry. After all, your first developer job should align with those goals as well so that you're on track for a longterm successful career.

Note: If you have already secured a job prior to graduation, skip to the second part of the plan below.

#1: 30-Day Job Search Action Plan

Create a schedule & goals for the first 30 days Post-Graduation

Design a 40-hour "work week" that provides time for:

Group Five

Session Title: Technology in the Media

Description: Why should students come to this session?

With terms like 'Russian hacking', 'bitcoin', 'net neutrality', and 'fake news' dominating the news cycle, what can we as developers do to help aid in understanding what these buzzwords actually mean.

Session Outcomes: What will students leave with or gain from this session?

Who Are You?

I am a developer-in-training with a passion for helping others! I graduated with a bachelor's degree in mass communications, but I found the field I studied, public relations, was not for me. I had issues with telling a story with facts, rather than presenting facts with analysis. My husband began sharing some of his work with me, and I developed an interest in programming. I went back to school part-time for computer science before my education was put on hold by a job and a move.

Why Are You Here?

I'm here to develop the skills to help others in a more meaningful way. Tech is changing very rapidly and there are many new opportunities to use new technology to solve long-standing problems. I want to use my background in mass communication and in the service industry paired with these new skills to help change the world for the better. I spent about a decade in the food service industry and slowly began making my way to the tech arena. I've learned a great deal from my tech jobs, but I was

#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.

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

	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?

	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?

	## 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.

	# 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.