Jlawlzz

Title

Header 1

This is a paragraph

header 2

This is paragraph two

Jlawlzz

So if the incident metadata is blank, just pass in an empty object: {}.

The bot will create the state from scratch as if it was starting a new conversation.

On output the bot will pass an object:

{
  outgoing_payloads: outgoing_payloads,
 state: {

Jlawlzz

##Models:

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

Jlawlzz

##Models:

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

Jlawlzz

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

Jlawlzz

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?

Jlawlzz

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

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

Jlawlzz

#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/

Jlawlzz

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