Maria St. Louis-Sanchez mariastlouis

This is my prework for Turing

HTML code describes the structure of the pages - by adding code it makes the web page take on the structure we want.
Tags are like containers, they tell you what lies in between the opening and closing tag. An element tells the browser information about what is in between the opening and closing tags. An element contains the opening and closing tag and everything in between them.
Attributes are used in elements to give more information about the content of an element.

Head: This contains information about the page. It is not shown in the browser.
Title: Contents in this element appear in the title bar or tabs.
Body: Everything in the main body element is show in the browser window.

29 Behaviors That Will Make You an Unstoppable Programmer"

While reading the article "29 Behaviors That Will Make You an Unstoppable Programmer" I realized that they basically listed the same behavior several times: admit when you don't know something and learn it. If you waste time pretending you know something, you won't get your job done and you won't have learned anything new. Instead, if you admit it, you can learn quickly, move on and you won't make the same mistake again. I think the other behavior that was mentioned several times was to be adaptable - you can't think you know everything and insist on doing things one way. Instead you need to know how to change when things aren't working, how to look things up when you hit a road block and, above all, keep on learning no matter what so you can always keep improving. Another great behavior was to stay on top of what's coming - this is by learning how to use tools to make your life easier, by talking and interacting with co-workers to learn from the

Build on your professional story by thinking about how you're progressing at Turing. Answer the questions below in your own gist to use your StrengthsFinder themes to add to your story:

Write 1-2 paragraphs about your StrengthsFinder themes: How have you seen yourself using these strengths at Turing? Has your understanding of these strengths changed since you first reflected on them? If so, how?

Being a 'learner' as my greatest strength, I continue to look for answers when I may not know them. This has been very useful as there is a lot I don't know and a lot to learn. I am also always seeking out not just a way of completing a project, but the best way of completing it. This comes hand-in-hand with ideation - also a strength -- which helps me connect the dots between different concepts and put them together. Many times here, I've felt that we're given a little information and expected to put everthing together ourselves. Thankfully, it's been happening so far.

Write a story about your Turing expe

Growth Mindset

I am so glad we started Turing with this Gear-up. Throughout the entire mod I kept on coming back to the lessons here and instead of telling myself I was terrible, I told myself I would learn, I would get there. I've had to become comfortable with being uncomfortable and knowing that there's a process to becoming a great programmer and it doesn't happen overnight.

Getting better at difficult things

What I took away most from this session was that the best way to learn something difficult is to learn from a master and immerse yourself in it. This was heartening to me, seeing that I feel this is what I am doing at Turing. It was good knowing that learning difficult things does take time and I don't necessarily need to be a master at it from the beginning. However if I surround myself and jump in the deep end, I might not drown.

Working with Introverts, Extroverts, and Ambiverts

Date of feedback conversation: Oct. 16 with Katie Scruggs

For this conversation, I prepared by first writing out what I thought just so I would remind myself what I had to say. I didn't use the notes for the conversation but they helped me get my mind organized first.

The conversation went great. Katie was a great partner and we got along well for the whole project. Just as we were starting to pair we had gone over again the strengths assesssment and realized that we had the same strengths - ideation. That was great because we were on the same page but I was a little worried that if we were both looking at the bigger picture that we'd have a hard time on the details. Thankfully that wasn't entirely the case. At one point or another, we both had to rein in the other one to keep from trying to do something huge to make sure we had something first that worked. At another point we both wanted a big change and were both willing to work harder to make the big change of course.

The conversation went well - we b

I really enjoyed learning more about agile practices as it directly relates to what we do here and what we will be doing in our future workplace. Talking about my strengths - and the strengths of my partner - helped us understand one another better as we were starting a new project. As it turned out, we had almost exactly the same strengths - but knowing that was good becasue we knew that we both had the same weaknesses (i.e. we like to think big picture and tend not to focus on details as much) so we worked hard to hold one another accountable and made sure we were staying on top of the weaknesses. It was also helpful because when we decided to make a big pivot we were both on board because we were both thinking of the big picture and how much better our project would turn out.

Before thise session, I had worked well with partners simply by talking with them often. After this session, I used Waffle.io to help keep track of issues and keep my partner and myself on track by always being able to see exactl

I'm a learner.

I started my career as a journalist, which was great because it was my professional duty to learn something new every day and share it with the world. In that job, I started to learn the power of data. I learned that numbers could be a better predictor of what was going on than what politicians and administrators were saying. For instance, I was once interviewing a principal of a school who only wanted to talk about how great his school was because they had a new mural in the gym. At the same time, he had the poorst-performing school in the district and no plan about how to improve it.

Because of this power of data, I transitioned my career to become a data journalist. I learned how to request data, analyze it and use SQL and spreadsheets to figure out what was going on with the numbers and use that information to drive my stories. That was great, but as I learned more I realized that it wasn't enough just to give people my analysis of the biggest trends, pacakage them into a 20-inch story

	Directions: Copy this template into your own gist.

	# Strengths Reflection & Coaching Request


	### Read Through Your Theme Definitions

	1. What words or phrases stick out to you? How would you define each of your top 5 talents in your own words?

	"You are energized by the steady and deliberate journey from ignorance to competence" - This is definitely true. I can be dead tired about to fall asleep, and yet when I start learning something new, I wake up again.

	# DTR: Define the Relationship

	Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.

	### Guiding Questions to Define The Relationship:

	* What are your learning goals for this project? What drives us in this project?
	* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
	* How do you communicate best? How do you appreciate receiving communication from others?
	* How would you describe your work style?