Skip to content

Instantly share code, notes, and snippets.

View hkim53's full-sized avatar

Hannah hkim53

  • NYC
View GitHub Profile
@hkim53
hkim53 / InterviewPrep.md
Last active March 20, 2018 04:35
Interview Prep

Interview Prep

1.) Do Your Research

  • Glassdoor
  • Facebook - look at their culture
  • Tumblr
  • Look at technical blogs
  • LinkedIn - look at interviewers' LIs.
  • Website - look at their website and talk about what you like
@hkim53
hkim53 / 12-principles.md
Created May 21, 2017 02:58 — forked from zcaceres/12-principles.md
Gregg Pollack's 12 Principles
  1. Expectations. Incorrect expectations are often why things fail.
  • Get client closer to the team
  • Short feedback cycles (weekly communication and estimates to keep project spec up to date)
  • Project management tools
  1. Be mindful of your inner problem-solver Someone comes to you with an idea, don't shoot it down by 'diagnosing' all the problems.
@hkim53
hkim53 / debugging.md
Created March 26, 2017 21:42 — forked from glebec/debugging.md
Debugging

Debugging JavaScript Applications

A practical distillation for Fullstack Academy students

Faults in computer problems were theorized as far back as 1843, when Ada Lovelace noted of Babbage's Analytical Engine, "Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders." Almost 160 years later, NIST reported that software errors cost the US $59 billion annually. Clearly, some of the cards are wrong. However, unlike Grace Hopper's famous moth, most of the time the culprit is ourselves.

Debugging is a sanitization procedure consisting of:

  • Preventing bugs in the first place, through good practices and assistive tooling.
  • Detecting bugs when they first arise, through proper error handling and testing.
@hkim53
hkim53 / debugging.md
Created March 26, 2017 21:42 — forked from glebec/debugging.md
Debugging

Debugging JavaScript Applications

A practical distillation for Fullstack Academy students

Faults in computer problems were theorized as far back as 1843, when Ada Lovelace noted of Babbage's Analytical Engine, "Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders." Almost 160 years later, NIST reported that software errors cost the US $59 billion annually. Clearly, some of the cards are wrong. However, unlike Grace Hopper's famous moth, most of the time the culprit is ourselves.

Debugging is a sanitization procedure consisting of:

  • Preventing bugs in the first place, through good practices and assistive tooling.
  • Detecting bugs when they first arise, through proper error handling and testing.