Skip to content

Instantly share code, notes, and snippets.

View Jlawlzz's full-sized avatar

Jordan Lawler Jlawlzz

View GitHub Profile
@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
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 / 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?