John Michael johnmboudreaux

A quick note

I chose to use the NASA api because I love anything outerspace. I check out their images through the NASA app daily. It gives me such an interesting feeling of wonder to experience a sense the vastness of the universe that we live in. It is a fun part of my day that I get to share with my wife an kid and also a tool that helps me keep the smaller one interested in space travel and exploration. I hope you enjoy it as much as I do.

Instructions:

This app will ping NASA's db and display for you their image of the day along with a title and description of what you are witnessing.

POST 30 PLAN

This will be my overview of my post Turing 30 Day Plan. The calendar (link below) that I have created for action step one in "creating a schedule" will contain my day to day activities which can/might be adjusted based off of talks with instructors or and schedule changes that happen with other people I interact with or any other un-avoidable things.

Google Calendar

Creating a schedule:

Action Steps

Palette Picker Submission Form

Project Spec

Basics

Link to the GitHub Repository for the Project

palette-picker

	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:

	What are you doing well as a pair programmer and collaborator?

	i make myself overly available. there are no spacial boundaries and i prioritize our project over most other things to make
	sure that we are successful.

	How do you use your strengths as a team member?

	if i have an idea that i know is good i can usally get someone on board. harmony is always one that makes sure everyone is happy
	so thats always a good thing.

	Francy and i spoke in early September

	How did you prepare for the conversation?

	I thought through it beforehand. my intent was to put myself in her shoes. i reflected a good bit on our interactions and
	prepared myself to make sure i didnt say anything that could potentially offend the other person while giving feedback.

	How did the conversation go for you?

	i thought it went well. it was pretty casual.

	just based off of my experience so far i can say that it is easy to write buggy code. i couldnt imagine writing code for months
	and months before being able to actually have it tried out by the end user.
	also the fact that code costs virtually nothing to produce, but when it works and serves some purpose its at least worth
	something. this means that it can be performing its intended dutyin less time.
	i personally cant think of how i implemented any agile practices into my projects. maybe i did and just dont realize it.

	The mentors/alums that I contacted were:

	Lovisa Svallingson 08/17/17 and 08/25/17
	Robert Cornell 7/20/17


	i met Robert for lunch. he is a lovelace mentor and offered to meet in the slack channel. so i did. we talked about how he got
	to where he is and some cool projects he is working on personall and professionallyas well as my story.

	i met Lovisa through my wife (they work together at CA) and i saw her name on the mentor sheet. i reached out to her and she

	I do really well with small attainable goals. In the last couple minutes of our time together set up a github gist and write
	down 3 actionable commitments you can do in your next coming projects to accommodate for accessibility issues?

	to date i havent really wraqpped my head around implementing ARIA. i did enjoy Jhun's lesson on it and it helped me understand
	what i am up against when writing accessible code.

	i should make sure the content is structured in a way that wiii make it easier for accessibility tools to will work well.
	i should make sure to include ARIA items in my code
	i should use tab index to make sure it is tab-able

	What are your learning goals for this project? What drives us in this project?
	jm-function refactoring and learning local srorage
	jorge-the same

	What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
	jorge-likes more indepedent programming. we need to find a balance we can both live with.
	jm-can go either way.

	How do you communicate best? How do you appreciate receiving communication from others?
	jm-slack, texting and face to face.