EMielke76

Challenge one: 
- Benefited heavily from the Big O lesson earlier today. Literally used the same build from the examples. 
- Found a built-in ruby method that did the thing for me `.intersection`, definitely be curious to know if built-in methods are allowed or not during challenges

Challenge two: 
- Paired with Kevin, worked collabrativelty through both our sessions
- Benefited greatly from having that collabrative experience, seeing how Kevin broke everything down to its very basic core before even writing a single line of code. 40min challenge, we pseudocode for 30min. Really great to see that process, and then to see it work.
- Second challenge, same process. Leaned on Kevin's appraoch, break it all down to the core before writing code, then starting dinking my way through it. Got it to work, which felt amazing. 

Challenge three:

EMielke76

AUTHENTICATION/AUTHORIZATION

What do you need to know about a “user” in a database table in order to “store” their data?

• Whatever the elements outlined in the table are, the incoming data must meet said elements. Correct data types, correct number of elements, etc. Depending on the data being stored, considerations of “uniqueness” must be factored in (only one user per email address, etc. )

How can we store a password in a secure way?

• Never as plain-text. Should the couple (login and password) be compromised, its game over right then and there if the password is stored as plain text.
• Some cases store the password in a database after it is encrypted via a reversible algorithm, though this is not suggested as it is “easy” to guess the logic of the encryption
• Hash encryption was popular for a while, however it can (and apparently was) be cracked by simple google searches of encrypted keys
• I think the simple answer to this question is “encrypting the password”, but I just finished reading about

EMielke76

B2 Intermission Work

Answer these Check for Understanding questions as you work through the assignments.

HTML

1. What is HTML?

• Stands for Hyper Text Markup Language
• HTML is the standard markup language for creating Web pages.
• Markup languages are basic computer languages that consist of easily understood keywords, names and tags that help format the overall view of a webpage. They're often written in human-readable synatx.

EMielke76

Checklist/Rubric

To make a copy of this rubric:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Part I: Creating Directories and Files; Initializing Git and Pushing to GitHub

• I named my directories correctly.

EMielke76

Eric Mielke's Mod 0 Plan for TOTAL DOMINATION

With only 3 class sessions remaining, Eric Mielke sets out to ensure he completes and passes Turing School of Technology and Designs's Mod 0! What will this entail you ask? Let us first take a look at what's left on the table.

Mod 0 Work yet to be completed (at the time of writing)

1. Session 3, session and homework
2. Session 4, session and homework
3. Session 5, session and homework

EMielke76

Session 2 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!

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.

EMielke76

Session 1 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!

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.