- In a few sentences, explain what the project was and the scope of your work. Imagine explaining your answer to a technical recruiter or a developer who you’d potentially be interviewing with who knows nothing about Turing.
- Our project was to create a tool for users to keep track of task and how much time it took them to complete those task. The user would be able to choose from three different activies mediate, study, and exercise. Our users then could enter a discription for that activity and input how much minutes and seconds into a timer input field. When the user starts activity they will be presented with a start button with the time it will take them to complete that task. The user then clicks start, once time is up they will be greated with a complet message and then a log button to log the activity.
- What is your approach to working on a team? (In your answer, provide an example from this project)
- My approach to working on a team is to set boundaries and understanding of working styles through DTR early. Caleb and I worked really well together because we followed each others DTR and we communicated when we did things or didn't do things. We also did our best not to snow ball the project, we did most things together.
- You can’t work out how to solve a coding problem. What do you do to find the answer?
- The first thing I do is check for errors. If there are no errors I resort to google and search the concept that I am trying to implement in my code. If I still have issues solving the problem I will lean on my co-workers and see if we can come up with an answer together.
- What is one technical takeaway from this project?
- If you understand what you are looking for and understand the code you will find your answer. My biggest take away is being able to complete a timer. Never did one before but my understanding of code made it easier to reaserch different concepts.