Week one at Turing was quite a challenge for me mentally, and it reflects in the amount of work I was able to do. However, I am challenging myself to stay positive, and acknowledge my accomplishments. During week one, I grew as a person by pushing myself to connect to others, and not be afraid to ask for help. I also have a better idea of what top-down-design and object-oriented-programming is. I have improved my googling and git/github skills significantly since mod 0. I have also learned how to utilize binding.pry. There's still a long way to go.
Ana Pérez Santos aperezsantos
aperezsantos
/ week_1_reflection.md
Created
October 7, 2019 15:23
Reflection on what I learned during the first week of Mod 1 at Turing.
aperezsantos
/ battleship_dtr_ana_daniel.md
Created
October 7, 2019 22:56
Template for DTR Memo Project: BattleShip
Group Member Names: Daniel Frampton, Ana Pérez Santos
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?):
- Top priority is learn
- Learn how to collaborate at our own pace as a team, and stay in sync
- Make parallel contributions
- Finish iteration 3
aperezsantos
/ week_2_reflection.md
Last active
October 14, 2019 01:52
Reflection for Mod 1 - Week 2
Something I am feeling better about is the git workflow in pairs as well as remote pairing. I am also significantly better at setting up test and lib files (not making them, as I already know how to do that, but inputting the initial code for each). One thing I need to improve is my logic when it comes to creating tests. I'm very frustrated with myself, as I am still having a difficult time remembering how to setup certain methods, after seeing them in the interaction pattern.
Project: Battleship - paired
Summary
Battleship is a partner project that introduces students to pairing through collaboration on building a battleship game. The game has multiple components, such as ships, cells, board, game, and runner. Using TDD (test driven design), partners build a battleship game in which a player plays with the computer. There are three main ways of pairing: driver/navigator,
My gains this week include having a better understanindg of hashes, specifically how to access information within them. I feel more comfortable with the creation of initial tests, and can understand the logic better, even if I cannot quite put my thoughts into code right away.
As I reflect on what I've accomplished thus far, I also recognize that I need to do further work on iterations/enumerables, specifically when to use which method. Also, ask more questions when I don't understand something.
aperezsantos
/ pd_futbol_project_feedback.md
Last active
February 27, 2020 17:58
Agile & Feedback Reflection - Group Project - Futbol (edited to include Cohort 2001 reflection)
In interviews, you'll be asked about how you approach working in projects, and being able to describe how you utilize agile processes is a great way to help you stand out as a junior developer candidate. This reflection is meant to help you develop this skill. With that in mind, please answer the following questions in your own gist about your group project:
-
What have you learned about the use of agile vs. waterfall in software projects? It requires plenty of communication for agile projects to work well. This statement is still true. Additionally, I would say that bringing different perspectives to a project is essential because it helps develop great ideas, and you have others to check your understanding.
-
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.)?
Goal (what is the goal): Specific (What do you want to accomplish? Who needs to be included? When do you want to do this? Why is this a goal?):
- Manage time more effectively - through setting daily learning goal(s), time blocking, using calendar/time management apps like toggl; because being organized, I can better manage my days, even if there are outside factors that are taking a substantial time away from coding
- Communicate needs more clearly - by asking for help earlier, asking questions, through regular check-ins with staff, other supportive individuals; because last inning I felt I was doing better, and so I stopped communicating regularly about those outside factors
- Take care of my mental health - by setting an hour or two each week to do something for myself, signing up for a session with Jun; because my mental health is important
Measurable (How can you measure progress and know if you’ve successfully met your goal?):
- By reflecting on a day's work and if I've met my learning goa
DTR
Project: Battleship, BE 2001
Group Member Names: Ana Pérez Santos, Ethan Hocking
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?):
Individual Ana - Be more comfortable working independently, while working in a colloborative project; complete iteration 3; learn to review code
aperezsantos
/ dtr_futbol_colin_mike_ana.md
Created
February 17, 2020 05:14
DTR for Futbol Project, BE, Cohort 2001
Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.
- What are each of our learning goals for this project? What drives us in this project?
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- How do you communicate best? How do you appreciate receiving communication from others?
- How would you describe your work style?