jakejakearell

1. Prepare for Job Experience: AEIOU

• Activities: what questions do you have about the activities that a software developer does on a daily basis?

  How much time do you spend in meetings? How much time do you spend in front of a screen?

• Environment: what questions do you have about the overall environment and culture of this workplace?

  How many hours a week do you typically work? Is there a commitment to building a more diverse workspace and if so what does that look like?

• Interactions: what questions do you have about the team at this company? What do you hope to learn during this experience?

jakejakearell

Mind Maps:

• i. Engagement. What did you reflect on last week in regards to when you're engaged in your work at Turing? The moment when I solve a problem that I previously didn't know how to do What are all the steps that go into that moment? When do you get to use your strengths? What is fun about this?

Usually the first step is recognizing I am stuck on something and take a step back. Sometimes that's a pom, meal break or just calling it a night and trying it the next day. I think then it is breaking down what the problem is and what I want to happen. Then seeing if I know how to code each part of the problem. If I don't know something I usually go to the codehelp channel and see if anyone has run into what I did and look for solutions there. If not I then try some targeted googling. If that doesn't work I will usually post in code help and my cohort mates are very good at responding. I think it is fun because I felt like I learned something, that I am in a community that will h

jakejakearell

1. Authentication

• you need to store a user in a database table; what do we need to know about them (ie, email, password)

  I think it would really depend on what you were making. This makes me reflect on working at the hospital when every patient needed to have first name, last name, date of birth and a unique medical record number so no one get entered as the wrong person. I guess the minimum would be enough info to be reasonably certain that a user is distinct. Username, email and password seem like the baseline based on my time on the web.

• how can we store a password in a secure way (ie, if our database is compromised, how can we protect their passwords from prying eyes)

I think this is where abstraction and encapsulation come into play. We need to store sensitive information for our apps to work, but we also need to make sure that users wouldn't really a way to access our databases from our view. I would imagine this is where encyption comes into play too-- if our database gets compromised pe

jakejakearell

Limit number of text messages sent per month

1. Where will you start in the codebase, and why did you decide to start there?

• This might be redundant but the place I am inclined to start at is the read-me so I can understand the frameworks they are using and just the general structure of the code. From there my instict was to look at the routes, see the controllers then look at the models. In this case I saw a outgoing SMS model so I started looking for where else that appeared in the codebase and try to map out the flow from there.

2. What is familiar to you about the codebase?

• It is a rails application so the architecture is pretty familar after two mods.

3. Are you making any assumptions? If so, what are they?

• Front end is handling the views for most of this app, the back end is just providing the information.