Skip to content

Instantly share code, notes, and snippets.

View bbp5280's full-sized avatar

Ben Porter bbp5280

  • Student at Turing School of Software and Design
  • Denver Colorado
View GitHub Profile

Ben Post Grad Action Plan

Areas of Emphasis

Due to the fact I am starting a job on Feburary 1st my action pland is based on prepping for success in this position. The Position is a full-stack position at a start up that runs a ruby/rails backend and a react front-end. While my focus will be mostly on the fron-end due to the size of the company I am sure I will be helping out anywhere it is needed.

The Daily plan consist working on JS challenges and past project issues for an hour or 2 in the mornings to keep sharp on the technologies I have already learned. From there I plan to spend another roughly 2 hours a reading up on and walking through ruby and rails tutorials.

At this point I do not have access to the companies repos. They have discouraged me from wanting to start familiarize myself with the code base before I am getting paid. I have a meeting on Moday in which I am going to verify that is there preference. If I do get access to the code base I will likly alternate code challenges with di

Palette Picker Submission Form

Project Spec

Basics

Link to the GitHub Repository for the Project

palette-picker

Link to the Deployed Application

Agile Workflow

  • In many ways the agile workflow at it's principle has been hard to follow this mod. With the projects being such quick sprints it is hard to get our applications in front of people for testing to then circle back and adjust. So often final aspects of functionality are coming together in the end and there is no time, and sometimes no energy to change them before evals. This does not mean that I do not see and appriciate the idea of the agile workflow, and there will always be excuses to only use part of if, I have just found it very tricky to impliment into projects currently. The parts of the workflow that have been working well for me are the make it work, make it right statagy. Every step of an implimentation has been run on this part of the workflow and has been essential to getting projects done. The other part that has gone well for me is the adaptive nature. If an earlier implimentation needs redone or adjusted based on tieing it to a later part I have been quick to accept it and get

Feedback III Reflection

  • What are you doing well as a pair programmer and collaborator?

    • A few of the things that I seem to be doing well in pairings include carrying my share of the work load, holding a clear understanding of the projects and being able to work in a range of styles. Not supprisingly I have been paired with a wide range of personalities, work styles, and understanding levels. In every case I have been able to be a segnificant contributor to the project and help drive it in the right dirrection. I feel that all my pairings have gone quite well.
  • How do you use your strengths as a team member?

  • I have found my strengths to be a real positive in my pairing projects. My learner strength and my ability to learn quickly have allowed me to carry a high level of understanding going into most projects. This has been helpful in getting the projects out to quick starts. While my adaptive strength has allowed me to adapt to the working style of my partners. For some projects we have been ab

Feedback II Reflection

  • Date of feedback conversation: 8/29/2017

  • How did you prepare for the conversation?

    • I prepared for the conversation by writting down a few key points for the conversation. The project whent really well so there was not a ton of coaching which is the part that is always the hardest for me. The major points I wanted to address mostly centered around making sure to speak out if I am not being clear in my comunication. I can find it hard to put my thoughts about the code into words, and several time my partner would say the next day "that's what you meant" and would imply they had stated they understood an approach I was taking when they did not. Sicnce we were able to break the project up so much and each takle our own objectives the projet did not suffer but I could see how it could have.
  • How did the conversation go for you? What was easy about the conversation? What was more difficult?

Mentor

  • Name of contact

    • The mentors I reached out to are Ireina Krammer and Dano Blanchard. This was a very soft cold outreach as they are both developers at companies I use to work for.
  • Date of contact

    • 08/21/2017

    • I heard back form Ireina within a few days and she has been a wonderful reasource doing screen shares with me to help on projects and just generally encourageing me when I am feeling lost.

Strengths & Storytelling Reflection Guidelines

Build on your professional story by thinking about how you're progressing at Turing. Answer the questions below in your own gist to use your StrengthsFinder themes to add to your story:

  • Write 1-2 paragraphs about your StrengthsFinder themes: How have you seen yourself using these strengths at Turing? Has your understanding of these strengths changed since you first reflected on them? If so, how?

*I was quite surprised at how accurate the strength finder quiz was, and what has stood out the most while here at Turing has been my learner and restorative strengths. Of course learning is what I am here for, but it goes beyond just the class sessions and the curriculum. I find myself thirsting and investigating how the other people around me approach the same problems, and their approaches to code. I feel the need to find out everything I can about different approaches even if they are not of use to my line of thinking with can mettle my direct

Project: Idea Box

Group Member Names: Ben Porter and Francy Lang

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

  • Use time productively, work on creating baby functions one at a time. Do the best that we can and each be able to articulate our way through the final code.

Goals and expectations:

  • To be more patient with ourselves and focus on what we have done and less about what we haven't or what we could have done better.
@bbp5280
bbp5280 / DTRmemo.md
Created July 30, 2017 21:04 — forked from francylang/DTRmemo.md
Francy and Ben's Idea Box DTR Memo

Project: Idea Box

Group Member Names: Ben Porter and Francy Lang

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

  • Use time productively, work on creating baby functions one at a time. Do the best that we can and each be able to articulate our way through the final code.

Goals and expectations:

  • To be more patient with ourselves and focus on what we have done and less about what we haven't or what we could have done better.

• Top accessibility commitments include, ensureing the use of semanticly segnificant html elements whenever possible, and adding tags, and attributes when not. • The need to run pages through a screen reader, as well as expericence the page by tabbing through. • The use of tools like axe and make me color blind to ensure visuals are ok.