Leo mrleolink

System Design Cheatsheet

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

Basic Steps

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?

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	/* Copyright 2019 The Android Open Source Project
	*
	* Licensed under the Apache License, Version 2.0 (the "License");
	* you may not use this file except in compliance with the License.
	* You may obtain a copy of the License at
	*
	* https://www.apache.org/licenses/LICENSE-2.0
	*
	* Unless required by applicable law or agreed to in writing, software
	* distributed under the License is distributed on an "AS IS" BASIS,

	# GIT heart FZF
	# -------------

	is_in_git_repo() {
	git rev-parse HEAD > /dev/null 2>&1
	}

	fzf-down() {
	fzf --height 50% --min-height 20 --border --bind ctrl-/:toggle-preview "$@"
	}

	#!/bin/bash

	# Runs the specified command (provided by the first argument) in all tmux panes
	# in every window. If an application is currently running in a given pane
	# (e.g., vim), it is suspended and then resumed so the command can be run.
	all-panes()
	{
	all-panes-bg_ "$1" &
	}

	import com.google.gson.Gson;
	import com.google.gson.JsonSyntaxException;

	import com.android.volley.AuthFailureError;
	import com.android.volley.NetworkResponse;
	import com.android.volley.ParseError;
	import com.android.volley.Request;
	import com.android.volley.Response;
	import com.android.volley.Response.ErrorListener;
	import com.android.volley.Response.Listener;