Dan Phillips dphilla

## danielphillips_prework.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                dphilla
                / danielphillips_prework.md
            
            
              Last active
              April 27, 2017 21:16
                — forked from mbburch/prework.md
            
              
                Daniel Phillips Pre-Work
              
          
    Turing School Prework

Task A- Practice Typing:


screenshots of scores will be posted in comments

Task B- Algorithmic Thinking & Logic:


screenshots of completed sections will be posted in comments

Task C- Create your Gist:


## gist:5d27d13a2ffe20a1a0d1bac08acbc2d6
# DTR: Define the Relationship

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?

## gist:9e7b213299d6fa6b01d160e1b63618ce
# 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:


* Look at your initial StrengthsFinder reflection that you completed in week 1 -- how have your perceptions of the top 5 themes stayed the same? How have they changed?

I think many of my perceptions of my top 5 themes remain unchanged, and I can definitely see how they can play out in writing software, at least in the little bit that I've done so far this Mod. The most striking is how I feel my Ideation component from StrengthsFinder plays out in how I feel relztively comfortable diagramming a project, but have to focus harder when Im in the weeds on it.

## gist:68db439667d2be574cc5cb0fa3c85915
1. a unique key on the table on given resource table
2. a reference to another tables primary key
3. a schema is visual representation of table relationships
4. a one-to-many relationship indicates that many resources "belong" to a single resource in another table, while a many-to-many
relationship indicates multiple resources point referencing other multiple resources
5. a foreign key on a table is a copy of/references the a single primary key on its own (native?/primary?/home?) table.

## AR_methods.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                dphilla
                / AR_methods.md
            
            
              Last active
              July 10, 2017 16:50
            
              
                Some New ActiveRecord Queries and Calculations 
              
          
    Brief AR Relation Methods Exploration

Play with the following with this https://github.com/dphilla/class_pets
order
.order("count_id asc").count(:id)

  
## gist:00e8419078b19cd85f8d680844cd37b1
Why do we namespace things?

We namespace when we want to separate the available functionality for a certain type of User on an app, or when we don't want
to repeate information that isn't pertinent to every user on certain pages.

What is the difference between namespacing and scoping?

scoping allows use to define the module, as well as the prefix assignment, while namespacing assumes we want
those elements be the same.

## simple_solidity.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                dphilla
                / simple_solidity.md
            
            
              Last active
              July 28, 2017 20:11
            
              
                solidity - shallow dive 
              
          
    Solidity

-around the room  re-intros
-are there any challenge sites? codewars, etc.
IDE

remix.etherium.org


## gist:4133411898249429af34d2a0afedeeb2
# Documentation Guidelines for Cold Outreach I Deliverable:

* Name of contact
  * The Alum I contacted is Tom Leskin

* Date of contact
  * 5/1/17

* Outcome (i.e., did you get a response? If not, what is your follow-up plan? Did you meet? When? What was the result?)

## gist:5c764697bfbc554f816af7da4def8038
In this Mod, we used agile workflow, specifically for our group projects, but I also tried to implement this strategy in
my own projects.

I think overall, the Agile process worked well, especially in our group projects where we had 4 teammates on a specific
project. This methodology worked well because it allowed us to constantly be moving the ball forward on the project, while
maintaining open communication throughout.

If there's one thing that I think I could have done differently, and one thing I'd like to bolster for future projects, it
would be my familiarity with git. I feel comfortable with using git locally and remotely, but I know there is a sea of
functionality that I'm not currently utilizing. This is something I plan on exploring soon.

## gist:5694e4e13cd43dc36cec1c1a080a0634
# Feedback II Reflection

* Date of feedback conversation: 7/5/17

* How did you prepare for the conversation?

         I had several thoughts from our groups work that I had been keeping track of prior to this conversation; otherwise
         I didn't do a lot of explicit preparation.

* How did the conversation go for you? What was easy about the conversation? What was more difficult?
	# DTR: Define the Relationship

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



	* Look at your initial StrengthsFinder reflection that you completed in week 1 -- how have your perceptions of the top 5 themes stayed the same? How have they changed?

	I think many of my perceptions of my top 5 themes remain unchanged, and I can definitely see how they can play out in writing software, at least in the little bit that I've done so far this Mod. The most striking is how I feel my Ideation component from StrengthsFinder plays out in how I feel relztively comfortable diagramming a project, but have to focus harder when Im in the weeds on it.
	1. a unique key on the table on given resource table
	2. a reference to another tables primary key
	3. a schema is visual representation of table relationships
	4. a one-to-many relationship indicates that many resources "belong" to a single resource in another table, while a many-to-many
	relationship indicates multiple resources point referencing other multiple resources
	5. a foreign key on a table is a copy of/references the a single primary key on its own (native?/primary?/home?) table.
	Why do we namespace things?

	We namespace when we want to separate the available functionality for a certain type of User on an app, or when we don't want
	to repeate information that isn't pertinent to every user on certain pages.

	What is the difference between namespacing and scoping?

	scoping allows use to define the module, as well as the prefix assignment, while namespacing assumes we want
	those elements be the same.
	# Documentation Guidelines for Cold Outreach I Deliverable:

	* Name of contact
	* The Alum I contacted is Tom Leskin

	* Date of contact
	* 5/1/17

	* Outcome (i.e., did you get a response? If not, what is your follow-up plan? Did you meet? When? What was the result?)
	In this Mod, we used agile workflow, specifically for our group projects, but I also tried to implement this strategy in
	my own projects.

	I think overall, the Agile process worked well, especially in our group projects where we had 4 teammates on a specific
	project. This methodology worked well because it allowed us to constantly be moving the ball forward on the project, while
	maintaining open communication throughout.

	If there's one thing that I think I could have done differently, and one thing I'd like to bolster for future projects, it
	would be my familiarity with git. I feel comfortable with using git locally and remotely, but I know there is a sea of
	functionality that I'm not currently utilizing. This is something I plan on exploring soon.
	# Feedback II Reflection

	* Date of feedback conversation: 7/5/17

	* How did you prepare for the conversation?

	I had several thoughts from our groups work that I had been keeping track of prior to this conversation; otherwise
	I didn't do a lot of explicit preparation.

	* How did the conversation go for you? What was easy about the conversation? What was more difficult?