Skip to content

Instantly share code, notes, and snippets.

View Jlawlzz's full-sized avatar

Jordan Lawler Jlawlzz

View GitHub Profile
@Jlawlzz
Jlawlzz / cfu_crud_in_sinatra.markdown
Created December 1, 2015 20:03 — forked from rwarbelow/cfu_crud_in_sinatra.markdown
CRUD in Sinatra -- Check for Understanding
  1. Define CRUD.
  2. There are seven verb + path combinations that are necessary in a basic Sinatra app in order to provide full CRUD functionality. List each of the seven combinations, and explain what each is for.
  3. Why do we use set method_override: true?
  4. Explain the difference between value and name in this line: <input type='text' name='task[title]' value="<%= @task.title %>"/>.
  5. What are params? Where do they come from?
1. Agile model places stress on dynamicism, communication, and faith in the people involved in a project,
to provide a more consistent, relevant, and quickly made project.
2. Software benifits from a lack of physical constraints, allowing us to adopt the most efficient development method
relativily quickly, this made it the ideal canidate for expirementing on process.
3. Many aspects of the agile methodoligy (mvp, small cycle production) actually had its start in auto manufacturers in Japan
earlier than when it hit software, testament to the ideas ability to be adapted to other industries. That being said,
one of the biggest bottlenecks for agile to work properly in any industry is a competent staff, and a trusting employer.
@Jlawlzz
Jlawlzz / gist:64457993eae1087a840e
Created December 7, 2015 19:07
Group Expectations TrafficSpy
Jordan Lawler, Brenna Martenson, JP Perry
1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
- Most anytime the group needs to work we are available outside of random small commitments. (Student Advisory board, DSA ETC.)
2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
- Slack for communication. Phones for necessary situations.
3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
- CSS: JP Asthethic Design w/ Brenna
@Jlawlzz
Jlawlzz / gist:034ff3bdff984fe23ef6
Created January 13, 2016 01:45
Jordan Module 2 Lightning Talks
Slack: Fact and Fiction
- Overview
- Implications of improper slack usage.
Slack: Customization
- Asthethic Customization
- Things to consider when uploading your sweet new emoji
- How to recognize a loading screen quote moment
- Notification Customization
- What to ignore, what to notify

#Jordan Lawler - M2 Portfolio

##Individual

Your Mission

I have always been a dreamer, with my inevitable trajectory entrepreneurship as a means to build and release products and services that (hopefully) change our world. Ideas remain just that without practical means of implementation, and Turing represents that next step for me. Over the next 7 months here my goal is to pick up the skill-sets and ideas necessary to begin my journey to this goal.

##Blog: http://jlawlzz.github.io/

##Leap

My code: (here)

Responder #1 (here) - This responder took the approach I first did, a single if else statement. I think this approach works fine for the task at hand and is certainly simpler than mine. Makes me wonder if I over-engineered my approach.

Responder #2 (here) - This user took a unique approach to this problem from what I have seen, using the boolean logic in a long chain attached directly to the return. While I do think this approach is efficient, I wonder about the readability of this approach.

Responder #3 (here) - This person went for a nested conditional approach. I try and stay away from a nested conditional as they can usually be broken out, and things can get hairy. As with the first user I think this apporach is

I think the rule allowing you to only instanciate one object per view, as well as the rule only allowing for 4 params to be passed through as arguments would be the hardest to adhere to.
- The rule pertaining to only instanciating one object for a view would be near impossilbe in some cases without creating meaningless glue classes to simply adhere to the rule. Some views have SO much info. I think this rule risks inadvertinly informing user experience. In my opinion that type of bleed is unaccessible, this rule should have a close eye kept on it for this reason.
- The rule saying only 4 paramaters can be passed also seems near impossible in my cases (like a form_for). This seems like the rule that would be broken the most, I am not sure there are work arounds for some of the instances when this rule would be broken.
@Jlawlzz
Jlawlzz / pr-template.md
Created April 11, 2016 22:39 — forked from rrgayhart/pr-template.md
Modified Quick Left PR Template

What's this PR do?

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

Screenshots (if appropriate)

What gif best describes this PR or how it makes you feel?

#Memoization

###What is it? At its most basic level memoization involves storing a value to prevent unnecessary work by identical calls in the future.

###Use:

  1. Memoization can be helpful when making duplicate database calls for static data. (like current_user)
- Example 1: 

##Models:

  • Album
  • Artist
  • Favorite
  • Follow
  • Genre
  • Like
  • PlaylistSongs
  • PlaylistTags