javolpe

I feel like I have become more aware of my habits, positive and negative. Like anything else the more you think about something the more aware of it you become. Just being aware of my habits has lead to more thought process about them and what I would like to keep vs change. As far as implementing new I'm starting small and just focusing on my morning routine and doing a decent job of hitting the snooze button less and gettting out of bed quicker. Drinking coffee in a different room helps to get the "start of the day" feeling sooner as well as incorporating body streching if not exercise. The results have been feeling more awake and prepared for the day.

Overall my health rating is a 3-4 depending on the week (5 being the best). Certainly more physical exercise could be useful, with Turing and everything else in life it is hard to find time but there is time to be found. I've been trying to exercise more regularly in the morning and need to do a better job of making that a firm habit. Outside of th

javolpe

What are each of our learning goals for this project? What drives us in this project?

Learn how to manipulate large sets of data. Incorporating new gems and tools ie specharness, SimpleCov, Hound CI. Get better at github collaboration and merging of code base. Enrichment learning and getting as far as we can. Everyone understands all of the concepts and the code base.

What is your/our collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

Due to the size of our group we will NEED to utilize both styles.

javolpe

Good software developer's are assuredly unique in innumerable ways but also likely do share some general traits. I believe those traits will likely include a propensity to continual learning and having a growth mindset, writing code that is empathetic to other developers who will come use the code after it is originally completed, reflection on their own biases and the biases of their team to try and limit those biases in code building practice, and a willingness to collaborate with other people's point of views. The habits a perosn would demonstrate to embody that idenity of a software developer would be habits centered around collaboration. Checking in with teammates to broaden understanding of non-technial ideas as well as technical ones.

My main goal as a software developer is to be a developer that other people want to work with (or at minimum don't actively NOT to work with me). Software isn't built in a silo, it's a collaborative effort, there will by times when something I am worki

javolpe

BATTLESHIP PROJECT

1. As far as things that went unusually well I would say probably two things. The first would be scheduling time to work together and the second being communication. We both were very accomodating of each other's time and schedulig preferences. We did almost exclusivley driver/ navigator and for that to work obviously both people need to be available and focused at the same moment in time. I felt that we both came to those sessions with a good attitude and drive to accomplish the tasks for the day. The second being communication, the bedrock of any partnership. We both seemingly communicated openly and honestly and I really felt that helped us avoid problems and issues. That communication builds and forms trust and I was happy with how we did in that regard.

javolpe

My social identity tells me that I probably share a lot of the same core values as others in the tech industry already. Mainl a drive to learn new things and keep improving myself. A desire for knowledge and to see logical things work. One of the big reasons I want to be in the tech industry is I'd prefer to be around a group of people where the barrier entry isn't privelege or wealth but rather drive and intelligence. To be successful in this industry a person has to work hard, be able to learn, and to some extent be a logical problem solver on top of the normal human emotional things associated with being on any team.

As far as my minuses go the one that stands out to me the most is obedience. The word itself bothers me. Obedience is different than working on a team or being employee. Being a teammmember means sometimes sacrificing for the good of the collective, that can take many different forms. Obedience is blindly following orders. Team cohesion and unity is something to strive f

javolpe

Project:Battelship

Group Member Names: Regina Casias

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?):

We both should end with the feeling that we contributed to the end-result of the project.  It shouldn't neccessarily always be I did this line or
they did that line but a feeling of unified completedness.  We both should walk away feeling like we learned new things and techniques too.
We should define success as at the end of the project we are happy with the outcome and both understand all of the code inside the project.

javolpe

1. One of my greatest honed skills is active listening and engaging. Having been in various sales and leadership positions I have learned how to actively listen to others and hone in on the details of what they are trying to get across. In previous roles that focus was aimed at finding how to meet their needs/wants but it can still be applied here. Having been in the construction industry, focusing on residential landscaping and roofing, I have expertise on best practices as they result to construction projects. This understanding can be generalized to project management of many other types. I have a strong natural ability to see things from a high-level and understand how various pieces connect and work together. The way to combine these is to readily understand best process and procedure for a given task or goal.

2. My Pairin top 4 confirm a lot of what I already think about myself. I love learning new things, I am truly interested in

javolpe

Career Journal for my time at Turing

Mod0

1. When you've worked towards a goal in the past, what systems or tools have been helpful for you in accomplishing that goal? How could you adapt those same systems/tools to use while at Turing?

The best system I've created for myself for accomplishing goals in the past is to think through where I want to end up and the different steps I need to do to get there. I have a tendency to get bogged down thinking about too much at once and will then procrastinate because it seems daunting and unachievable. By breaking a big undertaking into smaller portions it's easier to manage workflow and stay motivated. Often times I won't write it down but that's a behavior I want to change. List making and crossing things off is a satisfying visual way to feel accomplished. I'm not often lacking in the why I'm making big changes, self-reflection isn't my downfall. It's the staying on course and pushing through towards the end. At Turing a journal like this is a gr

javolpe

This is my top 4 qualities according to the Pairin survey.

javolpe

This is my first heading

This is my second and smaller heading

1. Item #1
2. Item #2
3. Item #3

• Bullet point
• Second bullet point
• One more for good luck