liambarstad

** Achievements
  My greatest achievement this module was finally tackling and correctly diagnosing the problems with my React Native app. I feel like I learned so much from the entire process, and I now feel comfortable approaching completely foreign technologies. Diagnosing these errors gave me a chance to re-evaluate the methods I use to attack problems, especially when those problems are poorly documented or obscure. My other achievements include giving a lightning talk on Amazon Web Services, learning JavaScript and React, and successfully connecting myself and others with fellow aspiring pythonistas. When problems were presented, I consistently tackled the more difficult ones, and I am not afraid to pave the way for others by researching and trying new ideas.
  
** New Interests
  I discovered this inning that I was actually very happy working with front end frameworks, and wouldn't mind taking a job described as Front-End or Full Stack. As well, there seems to be a lot of new ground to be covered in th

liambarstad

## DataFiend

### Pitch:

  It will be the goal of this project to successfully create a extensible neural network that can analyze and predict market trends across multiple currencies.
  
### Project Management:

  Pivotal tracker will be used to monitor iterations and gague the progress of the application.
  

liambarstad

DTR: Define the Relationship

Project: Le Pivot

Group Member Names: Dione Wilson, Hugh Morrison, Randal Springer, Liam Barstad

Project Expectations:

• Learn new things
• Develop proficiency with new communication tools/practices

liambarstad

### [Project Title]

JamHQ

### Pitch

JamHQ will be an application designed in the same breath as sites like Facebook and LinkedIn to allow musicians to share, collaborate, 
and connect directly with venues and producers.

### Problem

liambarstad

### [Project Title]

BlindChat

### Pitch

This is an app that will match people at random (I will also make a version that matches based off gender, orientation, and interests, to test its viability
as an actual dating app) and place them into a blind chatroom with each other, at which point they will have to talk to each other for a certain amount of 
time to reveal each other's photos.

liambarstad

Name of contact

  Alex Schaefer, Ryan Tyler, Bekah Lundy

Date of contact

  9/15/17

Outcome (i.e., did you get a response? If not, what is your follow-up plan? Did you meet? When? What was the result?)

liambarstad

(paraphrased and adapted from previously written and misplaced reflection)

This module, we have integrated the use of waffle cards effectively, most evident in our current project Little Shop. I think 
what made it easier to use waffle was the fact that, on this project, the spec was divided into user stories. User stories are
small, bite-sized chunks, that group members are not shy pulling down and completing. When the project was in whole iterations,
the tasks were often open-ended and more difficult to track progress. Regardless, more thought should have been given to dividing
bike-share more effectively. I have found since that it is much more effective to work in the same room with group members, but
seperately. That way, questions can be asked and answered quickly, but the whole group time is not spent laboriously going over
the plan. I enjoy the agile workflow, as it allows for greater compartmentilization and makes sure that each part of the program
is working before moving on to the next. It also me

liambarstad

Date of feedback conversation:

8/24/17

How did you prepare for the conversation?

  I had thought through what the outcomes of our project had been, where each team member needed to improve, and what they did
  well.

How did the conversation go for you? What was easy about the conversation? What was more difficult?

liambarstad

Currently, I am doing well at staying on top of group discussions and completing my share of the workload pre-emptively to 
minimize the stress later. I can be reliable, and helpful at answering questions. I have also become much better at pairing and
using the driver/navigator workflow to tackle problems faster. I am using my command trait in better ways, i.e. being less
territorial and authoritative, and being more inclusive. I have found it easier to work collectively and prop other members up
rather than divide myself to my own work. I would like to continue to develop this trait, to the point where I can seamlessly
pair and collaborate on tasks that require knowledge that team members have not yet fully integrated. As a team mate, I have 
noticed that, if I am left to my own devices, I will sometimes move forward to fast and neglect to leave space for my team mates
to work on and learn the material. This, I believe, is a failure of communication on my part, and I should always take the time
to run my pla

liambarstad

Setting Group Expectations

Group Member Names:

1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?

Group members can meet on weekdays until 7-8, preferring afternoons on weekends. Aaron will have to leave sometimes after school to watch his dog.

1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?