The application

The follow up

The thoughtful response

Getting the take home interview

The analysis of components / interview prep (3 days)

• Go back to at least one previous project that you want to update/refactor for your portfolio website. If you have past GH issues that you created, those can be a good place to start. Submit a link to your PR(s). Deliverable
• Refamiliarize yourself with the HTTP request-response cycle, watch this video.
• Refresh your familiarity with the git rebase workflow.
  • Read this article on git rebase.
  • Read this article on merging vs. rebasing.
• Submit your M4 Gear Up Lightning Talk here
• Complete the first draft of your cover letter using this cover letter checklist in preparation for your M4 professional developm

My name is Tyla Gillings. I am an active, outdoor enthusiast living in Colorado. Before jumping into Software Engineering, I was a mental health professional, working with young adults in residential treatment. My focuses included teaching individuals how to navigate emotional dysregulation as well as how to improve their self-esteem. I helped clients individuate from unhealthy relationships and dynamics as well as taught communication skills and life skills classes. I also enjoyed taking clients out hiking and on camping trips to unplug and reground themselves when needed. During the five and a half years that I worked in the mental health field, I also pursued a master's degree in clinical mental health counseling, part-time.

Sounds like a lot, right!? It was! However, I love how it has shaped me both in my personal life and in my professional career. I am grateful for the skills I have learned and can share with others. When shifting into Software Engineering, I found that the soft skills I brou

Answer these Check for Understanding questions as you work through the assignments.

1. What is HTML? --is a language which creates a web page structure; includes many elements
2. What is an HTML element? --html elements are components that hold important document information such as html, head(holding the meta info), title(for whole doc), body(all displayed info) as well as header or h1 and paragraph or p

What have you learned about the use of agile vs. waterfall in software projects? The agile approach seems to be much more realistic and parallel with work expectations and work-flow as they actually occur. Waterfall seems to follow it's own flow regardless of whether or not that matches what is actually happening with a project. I definitely prefer the agile approach, as it is more supportive of real-time work flow and expectation.

How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)? Project management in this group was less structured than what I would have liked which lead to ambiguity. While we attempted to start with a strong structure, clear expectations regarding work flow, and clear expectations about communication, after the second day or so, the group began to shift and mold based on various personality types. This piece drove the group dynamic, work-flow, and unintentionally redefined expect

Template for DTR Memo Project: Battleship

Group Member Names: David Lopez and Tyla Gillings

Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): Achieve- want to be able to work in a group setting for projects- being successful means completing iteration 3, Team strengths & collaboration styles (consider discussing your Pairin qualities here): David brings a stronger tech background and feels like he can guide others in the knowledge side as well as ask for help

• For my initial self-scoring, I gave myself a 2 for Functionality, 2 for Ruby Mechanics, 3 for Ruby Conventions,
• 2 for Testing, and a 2 for Version Control.
• After reviewing peers and having peers review my project, I came to the same conclusion and did not change any
• of my original scores.

Strengths_based_Essay

Pairin Top Four

When it comes to jumping into a new learning environment, workplace or even just working your way up within an organization, it is important to know what strengths you have, what you are good at, where you struggle, and how best to improve those qualities or skills based on your particular style, personality and world-view. For this element of the Mod 0 Capstone, here at Turing School of Software and Design, I participated in a two-part, Pairin Survey, and reflected over my personal results. At the end of the assessment, Pairin gave me a set of results that laid out my highest qualities within four categories: thinking style, drivers, emotional intelligence and virtue classes. Along with depicting particular qualiti

As a professional who has been working in the mental health field for over five years and is now stepping back from that to pursue a career in software development, I cannot emphasize enough how important interpersonal skills are in every workplace. Interpersonal skills can encompass a variety of skills such as communication skills, self awareness and empathy. Self awareness in itself can include awareness of one’s actions, behaviors, demeanors and reactions. As well, interperson- al skills include the ability to self-regulate in a time of conflict, where utilizing empathy towards others can be most difficult, though imperative to navigate such conflict in a healthy, productive manner, to move towards a common goal. As is described by Anne Spalding (n.d.), empathy is the ability to “put yourself in someone else’s shoes or to see the world through the eyes of someone else.” Why is this important in the tech field? Well, it’s important in every workplace, e