Skip to content

Instantly share code, notes, and snippets.

View collinkallery's full-sized avatar

Collin Kallery collinkallery

View GitHub Profile
@collinkallery
collinkallery / mod_0_session_1_readings.md
Last active August 15, 2019 23:21 — forked from damwhit/mod_0_session_1_readings.md
Mod 0 Session 1 Readings

Session 1 Readings and Responses

The readings and responses listed here should take you approximately 60 minutes.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of this document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

1. Learning Fluency by Turing alum Sara Simon (30 min)

  • Your key take-aways OR how you're going to implement specific points (minimum 3):
  • One of the best ways to learn about software is to jump all the way in and immerse yourself, like we are doing at Turing.
@collinkallery
collinkallery / guide_to_git.txt
Created August 22, 2019 22:47
Beginner's Guide to Git
# Beginners Guide to Github and Git
## Welcome to your high-level guide to understanding how to work with Github and Git!
Git is a **wonderful** tool that is used by most software developers in today's world. It can help you with the following:
+ Pushing out smaller pieces of code rather than one huge piece of code (_which can help minimize mistakes!_)
+ Working on your projects in different places - by using Github you will be able to push your projects online and then move to another computer to work on it later.
+ Work on projects collaboratively with groups of people - Github, being a public online resource, will allow you to share your projects with others so they can review and help out with your work.
## Example of a git workflow: Step by Step!
1. From your command line, make a directory with two files inside.
2. Initialize git, and your two files, and make an initial commmit.
3. Use your text editor to open one of the files.

Session 3 Practice Tasks

The assignments listed here should take you between 1.5 and 2 total hours.

To start this assignment:

  1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
  2. Click the Edit button when you're ready to start adding your answers.
  3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Professional Development:

Pairin Survey

My greatest strength from the Pairin Survey appears to be that I am ENTREPRENEURIAL. I know this because after taking the sruvey, I received an email saying that this was where I scored highest. I work best through inspiration and imagination - I work well in trial-and-error formats where I can test out different solutions to a problem. My greatest area of improvement is that I should ask for help more from others - I can definitely see this being highly important at Turing. While at Turing, I hope to put my imaginative working styles to the test with front-end software engineering! I am excited to think of an end-goal, or finished product that I want, and figure out and devise a plan working backwards from the finished product to eventually get there. I also love to take on different roles, so I think at Turing and in my future in software engineering I will adapt well to leadership positions, supportive positions, and everywhere in-between. Knowing about my

Gear Up

Empathy

Empathy has played a huge role in my life, specifically in my previous work. Throughout college, I worked in the field of mental health - specifically with kids with autism. Empathy was unbelievably important here because I needed to place myself in the shoes of the kids I was working with to efficiently help them and understand where they were coming from. I've also understood over time that empathy is important in any relationship, whether that be romantic, familial, or professional. There will always be a time when you disagree with someone that you are close with, and empathy is what allows us to reach common ground when that happens. If you do not have a compassionate perspective during times of disagreement, things could be said that you later regret. One specific example of how empathy builds better software is in UI/UX. Empathy is highly important here because you need to be able to place yourself into the shoes of another human and think about what they might like to see whi

Professional Practice - Read Three Blogposts

Dom Manipulation

While reading about DOM Manipulation, I learned quite a few new things from what I had already learned in class. First of all, DOM Manipulation refers to the Document Object Model, "which is the root of all objects on the web page...[and] represents the structure of a document and connects the page to the programming languages." One thing that I learned is that you can actually create document elements through DOM Manipulation, which I did not know. To do this, you simply document.createElement and this will create a new element for you. On the first blog post, the author decided to do a very simple rundown of what exactly DOM is at its most basic level. The second blogpost was centered around the idea that rather than using jquery, DOM manipulation can be used instead. This author also then went into the basics of DOM Manipulation, but significantly more in-depth than the previous author. A third author chose 15 DOM manipulation methods and

@collinkallery
collinkallery / Kallery.md
Created December 2, 2019 00:27
Fall Break Exercises

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 each of our learning goals for this project? What drives us in this project? Having a clearer understanding of javascript and how to implement flexbox. What drives us is our need to understand the basics of how these languages work together.
  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? Our collaboration style is a mix of pairing and individual time to solve problems. Specifcally, when given a problem, we will both work to take individual time to think about the issue at hand before discussing it together. We believe in a healthy balance of both pairing and divide and conquer. Being on the same page before pair and programming is very important.

Pair Project Reflection

Abstract

This project was called Intention Timer - an application where a user can pick a specific category on which they'd like to focus on (study, meditate, or exercise), specify what they will be working on with a short description, and also specify the length of time they will be doing the task. This application implements the use of a countdown timer entirely built from Javascript. Once the time is up, the user has the option to log the activity, and have it appear on the right hand side of the screen for later viewing. This implemented the creation of a Javascript class for Activities, which created a new instance of the activities class every time a user pressed "log activity."

Working on a Team

Since I have repeated mod1, my understanding of working on a team has been refined. I think I see many more benefits to working on a team rather than independently. During this project, my partner and I agreed that for the very most part, we'd work entirely together - two he