Skip to content

Instantly share code, notes, and snippets.

View Tman22's full-sized avatar

Taylor Moore Tman22

16 followers · 17 following
View GitHub Profile
@Tman22
Tman22 / gist:c57d6969a19d2c5b9ac583e59228e404
Created May 20, 2016 15:41 — forked from stevekinney/gist:9e9cfeb225c8133fda73
**Step One**: Watch [Sorting Algorithms in JavaScript](https://www.youtube.com/watch?v=uRyqlhjXYQI)
**Step Two**: Fork this gist.
**Step Three**: Respond to this question in your fork: "What are some of the balances and trade offs between different sorting algoritms?"
**Step Four**: _Totally Optional_: take a look at some of the other forks and comment if the spirit moves you.
@Tman22
Tman22 / gist:747b1177613ebd68a62c
Created December 7, 2015 17:31
Agile vs Waterfall
1. Agile is more flexible through the project. It keeps the business people and developers collaborating throughout the project, allowing for a more efficient and effective model. Agile delivers working software frequently instead of one finished product. This helps the customer better understand what the final product will look like.
2. Customers are able to see the software and help in the developing process. From what I've been told, projects will change scopes frequently. If you have an agile process it will be easier to adjust the software.
3. I believe it could be used for most industries.
@Tman22
Tman22 / gist:7204b82dafad932e6e7a
Created December 7, 2015 17:31
1. Agile is more flexible through the project. It keeps the business people and developers collaborating throughout the project, allowing for a more efficient and effective model. Agile delivers working software frequently instead of one finished product. This helps the customer better understand what the final product will look like.
2. Customers are able to see the software and help in the developing process. From what I've been told, projects will change scopes frequently. If you have an agile process it will be easier to adjust the software.
3. I believe it could be used for most industries.
@Tman22
Tman22 / 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?