Luis Garcia garcia50

ON GOING

29 Behaviors

Google’s my life! Its definitely not a coincidence that its first on the list, for me its always a go to first. I’ve already understood so far through the pre-work that google can become a very helpful and valuable resource to use. The next behavior that resonates with me as an upcoming developer kinda started on its own, the reason being is that I never liked to waste my time and I like to be as efficient with it as I am mindful of the value that it holds. “Code is cheap”, I have already witness this experience in the game we built for our pre-work and in other practices I took. I can definitely resonate with a lot of these behaviors and I know I was supposed to pick 3 but I feel like the 8 and 29 behaviors can be similar. Before anyone can admit it, I guarantee you I’ll be the first to admit that “I don’t know”…seriously I don’t! I’m a little overwhelmed on how much information there is and how much there is to learn, and thats where the “Move Fast and Break Things” behavior com

	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.
	Guiding Questions to Define The Relationship:
	What are your 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?
	What are your strengths? How can our strengths complement each other?
	What’s gone well or poorly in your previous projects?
	How will we set direction and make decisions as a team?
	How will we overcome obstacles?

	DTR Memo
	Project: Black Thursday
	Group Member Names: Adrian, Luis, Young
	Project Expectations: What does each group member hope to get out of this project? Goals and expectations:
	I expect to learn as we work on the project not only through my own work, but through the work of my partners.
	I also expect to finish it. Young- finish, Gitworkflow, learn to use branches. Adrian Organize + readable.
	Schedule Expectations: When are we available to work together and individually?
	I'm open everyday of every hour except sunday mornings.
	Young - available most afternoons
	Adrian - Doesn't like to wake up early.

	I've seen myself using my ability(stength) to be able to study for long periods of times throughout the day wihtout
	losing momentum. Another strength I have is having patience of which I've probably practice the most while at turing.
	As of now my uderstanding hasn't really changed except that I'm more aware of my strengths and how often I practice them.
	Since the start of turing my struggles haven't ended, and so far I've dealt with it by putting my strengths into practice.
	To be completely honest, I'm not entirely sure I have felt success since the start of the program, which I believe thats kind of the point in the struggle Turing wants us to endure, but overall I still trusting in the system. My story at Turing ends with me "on the other side"(next to the others who successfully graduated), I will continue seek growth in every job and position I take. My first goal, an most important goal, is to land that first job, where ever it may be. Story telling is never a hard thing for me, but I do personally belie

	Project: NightWriter

	Group Member Names: Anna Montoya, Luis Garcia

	Project Expectations/Goals: What does each group member hope to get out of this project?
	Completion, more comfortability loading text files, learn new strategies for breaking the problem into smaller pieces, gain familiarity using branches and merging to GitHub.

	Team strengths: Both have flexible schedules, Anna feels confident in writing tests and making sure the project meets spec expectations, Luis feels comfortable writing single responsibility methods.

	How to overcome obstacles:

	Luis Garcia 1711-BE

	Think back to last module compared to this module. How have you changed? How have your strengths helped you with your progress? Where are you stronger now than on day 1 of last module? Think about your progress both in terms of your technical and professional strengths.
	When's it comes to change I definitely notice the difference between where I was at-at the beginning versus where I am at now. I've definitely grown in skill and confidence.
	Allowing myself to focus on my strengths has given me the advantage and extra push I needed to be more successful this time around.

	Even though your Turing story isn't finished yet, what do you envision for your development in future mods? How will this story end?
	With an even more stronger foundation this time around I feel like I can see myself making it through the next upcoming mods. Like Alana’s story I too feel and have the hope that I can become successful through the rest of my journey here at Turing.

	Finally, write a draft of your story her

	Project: Little Shop Redux

	Group Member Names: Anna Royer, Luis Garcia, Luke Chambers

	Project Expectations: What does each group member hope to get out of this project?

	Goals and expectations:
	* Get a better understanding of Active Record
	* Get a better understanding of Sinatra
	* Get comfortable writing model tests in RSpec and feature tests in RSpec/ Capybara