Chapters 1 & 2
On a website, what is the purpose of HTML code? To frame webpage elements What is the difference between an element and a tag? tags label elements and act as a point of reference in the code Why do we use attributes in HTML elements? to further define elements and their attribtes or attributes tell us more about elements Describe the purpose of the head, title, and body HTML elements. body - everything insdie this element is shown in the main browser window
| 1. #10 It can be hard to commit to just getting something working when you know there is a better way of doing it. #10 resonates with me for this reason. | |
| #6 Again, code being cheap is another useful piece to understand if you tend to be some kind of perfectionist. | |
| #9 I know from experience that being able to debug is a very valuable skill. Thus being able to effectively read error messages is key. | |
| 2. I often used checklists in my old job, it was absolutely critical given the complexity of some insurance products and when gathering health information to get an accurate quote. | |
| I think in programming, given its complexity as well as all the moving parts also benefits enormously from having a structured approach to every project. Especially since | |
| there are a number of procedures that will never change no matter the project. | |
| 3. Strengths based development seems to, as a baseline, hire talented people. With that minimum threshold met, the management style can then focus on developing a more pos |
| **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? | |
Description of approach // this is a paragraph is Markdown Challenge number // this is a link in Markdown.
Strengths: Resourcefulness, refactoring, planning
How to work with someone else: Be highly involved in the planning/draft process to avoid pitfalls. Get the big pieces out of the way so we can focuso n finer details and features.
Communication: Just being clear on expectations
Workflow: Ping-pong, division of features
Dif Person: Just establish process and expectations
| Strengths & Storytelling Reflection Guidelines | |
| 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? | |
| A collector of facts, obsessed with the distilation of ideas, a thinker, a learner and adaptable. I see this helping me at turing when the time comes for the really conceptually difficult leasons. My ability to absorb these ideas and then distill them for others might prove invaluable in my cohort. However the caveats here are my tendancy to get bored once i understand a subject and no longer feel challenged by it, or how adaptability can also mean I have a hard time setting boundries with others and telling them no. I have to be careful to not spread myself to |
| Where I am - I've been successfully using semantic HTML and have tried to incorporate roles as well. | |
| Where I want to be - I think I'd like to investigate how to better utilize tab indexing and help the visually impaired. |
| Project: 2DoBox | |
| Group Member Names: Ben Porter & David Ryan | |
| Project Expectations: What does each group member hope to get out of this project? | |
| Goals and expectations: Solidifying our understanding of the material through exposure to another codebase. Utilizing kanban boarding to organize the project and distribute workload as well as enhance the ability to work remotely. | |
| Team strengths: Both strong logic skills with some previous familiarity of programming. Strong communication. Willingness to adapt. |
| Documentation Guidelines for Cold Outreach I Deliverable: | |
| Name of contact | |
| "The mentor (or alum) I contacted is Daniel Glauser" | |
| Date of contact | |
| "08/16/2017" |
| Turns out we used a sort of agile practice in Game Time. Instead of wading through the project trying to account for every little thing, we shot immediately for a working product that we could then refactor and itterate on to get it to where we want. We paired on the initial implementation then I handled refactoring mostly and Adam handled the testing. |
