smariapena

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

vinkla

Upload images to GitHub

1. Create a new issue on GitHub.

2. Drag an image into the comment field.

3. Wait for the upload process to finish.

4. Copy the URL and use it in your Markdown files on GitHub.

smariapena

Tester Questions

Style/Opinion/Purview

• Do you have a smartphone, what’s your favorite app? How would you test it?
• Tell me about your favorite bug that you found and reported.
• What are the benefits of an exploratory approach to software testing? Downsides?
• Where do test cases fit into your typical project lifecycle in an agile project in the client services world?
• Where does design fit into your test coverage strategy? How do you work with designers?
• Do you have any view on QA versus QC versus Test nomenclature?

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

natelandau

#  ---------------------------------------------------------------------------
#
#  Description:  This file holds all my BASH configurations and aliases
#
#  Sections:
#  1.   Environment Configuration
#  2.   Make Terminal Better (remapping defaults and adding functionality)
#  3.   File and Folder Management
#  4.   Searching
#  5.   Process Management

datagrok

Ideas for improvements to git log --graph

I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.

Make the graph for --topo-order less wiggly

Imagine a long-running development branch periodically merges from master. The git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.

It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.