You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chapters 1 and 2 on Structure and Text from HTML and CSS: Design and Build Websites
On a website, what is the purpose of HTML code?
HTML is used to provides/describes the structure of a web page. It dictates how browsers will display the elements of a page.
What is the difference between an element and a tag?
Opening and closing tags are like containers that tell you something about the information between them. They are the markers that an element is starting or ending.Elements are comprised of the opening and closing tags as well as any content that lies between.
Why do we use attributes in HTML elements?
Attributes provide additional information about the element. Attributes consist of the attribute name as well as the attribute value. These tell the browser something specific about how to handle the element.
Describe the purpose of the head, title, and body HTML elements.
Empathy plays a critical role in my life, but like many I am not my most empathetic at all times. It is easy to be empathetic to friends, it is what makes me a go to person for many of my friends when they need help or just someone to vent to. However, at times when I am overly self involved, be it from stress, a shortage of time, or any number of other reasons, empathy can be short. This can be even more true when you are not close to or even know the person who could use the empathy. On a normal day I may pass someone on the street who could use some help, notice, and have the empathy to want to help, but when things get busy and I am self absorbed I may pass the same person on the street and not even notice them. Empathy especially “compassionate empathy” can be a very powerful tool which everyone can use to help the world we live in a better place. We all need others to feel empathetic and helpful towards us at times, and it is crucial that we return the help to people both known and unk
• Top accessibility commitments include, ensureing the use of semanticly segnificant html elements whenever possible,
and adding tags, and attributes when not.
• The need to run pages through a screen reader, as well as expericence the page by tabbing through.
• The use of tools like axe and make me color blind to ensure visuals are ok.
Project Expectations: What does each group member hope to get out of this project?
Use time productively, work on creating baby functions one at a time. Do the best that we can and each be able to articulate our way through the final code.
Goals and expectations:
To be more patient with ourselves and focus on what we have done and less about what we haven't or what we could have done better.
Project Expectations: What does each group member hope to get out of this project?
Use time productively, work on creating baby functions one at a time. Do the best that we can and each be able to articulate our way through the final code.
Goals and expectations:
To be more patient with ourselves and focus on what we have done and less about what we haven't or what we could have done better.
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?
*I was quite surprised at how accurate the strength finder quiz was, and what has stood out the most while here at Turing has been my learner and restorative strengths. Of course learning is what I am here for, but it goes beyond just the class sessions and the curriculum. I find myself thirsting and investigating how the other people around me approach the same problems, and their approaches to code. I feel the need to find out everything I can about different approaches even if they are not of use to my line of thinking with can mettle my direct
The mentors I reached out to are Ireina Krammer and Dano Blanchard. This was a very soft cold outreach as they are both developers at companies I use to work for.
Date of contact
08/21/2017
I heard back form Ireina within a few days and she has been a wonderful reasource doing screen shares with me to help on projects and just generally encourageing me when I am feeling lost.
I prepared for the conversation by writting down a few key points for the conversation. The project whent really well so there was not a ton of coaching which is the part that is always the hardest for me. The major points I wanted to address mostly centered around making sure to speak out if I am not being clear in my comunication. I can find it hard to put my thoughts about the code into words, and several time my partner would say the next day "that's what you meant" and would imply they had stated they understood an approach I was taking when they did not. Sicnce we were able to break the project up so much and each takle our own objectives the projet did not suffer but I could see how it could have.
How did the conversation go for you? What was easy about the conversation? What was more difficult?
What are you doing well as a pair programmer and collaborator?
A few of the things that I seem to be doing well in pairings include carrying my share of the work load, holding a clear understanding of the projects and being able to work in a range of styles. Not supprisingly I have been paired with a wide range of personalities, work styles, and understanding levels. In every case I have been able to be a segnificant contributor to the project and help drive it in the right dirrection. I feel that all my pairings have gone quite well.
How do you use your strengths as a team member?
I have found my strengths to be a real positive in my pairing projects. My learner strength and my ability to learn quickly have allowed me to carry a high level of understanding going into most projects. This has been helpful in getting the projects out to quick starts. While my adaptive strength has allowed me to adapt to the working style of my partners. For some projects we have been ab
In many ways the agile workflow at it's principle has been hard to follow this mod. With the projects being such quick sprints it is hard to get our applications in front of people for testing to then circle back and adjust. So often final aspects of functionality are coming together in the end and there is no time, and sometimes no energy to change them before evals. This does not mean that I do not see and appriciate the idea of the agile workflow, and there will always be excuses to only use part of if, I have just found it very tricky to impliment into projects currently. The parts of the workflow that have been working well for me are the make it work, make it right statagy. Every step of an implimentation has been run on this part of the workflow and has been essential to getting projects done. The other part that has gone well for me is the adaptive nature. If an earlier implimentation needs redone or adjusted based on tieing it to a later part I have been quick to accept it and get