- screenshots of scores will be posted in comments
- screenshots of completed sections will be posted in comments
Zack Forbing zackforbing
zackforbing
/ zfprework.md
Last active
May 7, 2016 21:49
— forked from mbburch/prework.md
Zack Forbing's Prework Gist
zackforbing
/ week_3.markdown
Last active
May 26, 2016 17:22
— forked from worace/week_3.markdown
Module 1 Week 3 Diagnostic
This exercise is intended to help you assess your progress with the concepts and techniques we've covered during the week.
For these questions, write a short snippet of code that meets
the requirement. In cases where the question mentions a "given"
data value, use the variable given to refer to it (instead of re-writing
the information).
zackforbing
/ how_the_web_works_1605.md
Last active
June 29, 2016 23:00
— forked from Carmer/how_the_web_works.md
- First let's read MDN HOW WEB WORKS.
- Next let's watch a few quick examples of how the internet works.
- And [how IP addresses work](https://www.youtube.com/watch?v=KFooN7Mu0IM - how IP addresses work).
- Finally let's tie these things together and watch a video about DNS - what happens when you type an address into a web browser.
zackforbing
/ git-workflow.markdown
Created
July 5, 2016 20:57
— forked from erinnachen/git-workflow.markdown
My Git Workflow
- Load/Reload waffle.
- Choose a card from the backlog in waffle. If we're working separately, it's best to move that card that you've chosen into ready and perhaps assign it to yourself as well.
- git checkout master
- git pull origin master
- run rspec
- Checkout a new branch and tag it with #issue_number
- Write the feature test associated with your waffle card.
- Run rspec, and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
- commit your feature test
zackforbing
/ setting_expectations.markdown
Last active
July 6, 2016 14:55
— forked from Carmer/setting_expectations.markdown
Setting Expectations for Rush Hour
Group Member Names: Zack Forbing, Garrett Smestad, Pat Wentz
- 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?
It seems like we will all be able to work as late as necessary and as early as necessary. the only conflict was tonight Garrett had to leave so we are all brushing up on ActiveRecord.
- How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
zackforbing
/ Rush Hour Group Retro.md
Created
July 11, 2016 15:01
Team Members: Garrett Smestad, Patrick Wentz, Zack Forbing
What went well?
we worked really well in a trio, with everyone contributing. there wasn't really any conflict in the group, and we were all very committed to producing a quality product in the end. git workflow went well too, with only very few conflicts to manage.
What didn't?
patrick drove a lot, and wanted the rest of us to take a little more of a lead. getting distracted by small issues that one of us should have solved on our own.
zackforbing
/ MVC_in_Rails.md
Created
August 4, 2016 21:51
MVC in Rails: The Model-View-Controller Framework
One of the hallmarks of Module 2 at Turing is learning the MVC, or Model-View-Controller Framework. Learning the ins and outs of this framework will help a budding developer become a more effective architect of his projects. This sat well with me, as I discovered in Module 1, when one of my biggest weaknesses on projects was knowing where to begin. The MVC is essentially a design template for Rails, as it dictates three different types of objects and how they interact with one another - Models, Views, and Controllers. Each component has a distinctive job in Rails, and their appropriate handling and separation will help you create code that is cleaner, more portable, and more maintainable.
If the MVC thought about iterms of the request/response cycle, it might be more appropriately named the CMV model, as the request cycle goes from the browser to the controller, then to the model (and database). once the data is acquired, the controller passes the data to
zackforbing
/ notes from tech interview session.md
Created
September 22, 2016 18:55
first round / screening interview
- purpose: vetting on skill and interest, look for red flags, narrow the field so less time is wasted interviewing
-
- over the phone
-
- 30 min or less
-
- conducted by HR
-
- possible homework assignment second round - the scary part
- multiple sessions, commonly about 4 hours total
- one non-tech session
- two or more tech sessions
zackforbing
/ portfolio deliverables.md
Created
October 5, 2016 20:07
what am I looking for in my first dev job?
my top three priorities are working for a company that is doing things that I am in support of, is active in mentorship, and is in support of the advancement of my learning while I am working with them. I want to work for a company that I am not ambivalent about. I want to feel like I am helping to change the world for the good. As a relative newbie to coding, I also want to experience direction and insight from more experienced coders. finally, I have not learned all I need to learn, and I know that it is difficult for me to spend my spare time doing that when I am doing it all day, so I’d like to work for someone who is interested in helping me learn.
barriers:
entering the industry: feeling like a newb, not having any experience
stop this: there will always be people above AND below you. and you DO have experience, and you will get more as you go.
zackforbing
/ es6-research.markdown
Last active
October 8, 2016 20:50
— forked from anonymous/es6-research.markdown
OlderNewer