r17x

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?

r17x

Install and Create Emulators using AVDMANAGER and SDKMANAGER

TL;DR

For generic skin emulator with default apis (without google apis):

1. List All System Images Available for Download: sdkmanager --list | grep system-images

2. Download Image: sdkmanager --install "system-images;android-29;default;x86"

r17x

Basic Tmux Usage

https://tmux.github.io/ <-- Tmux project

http://z.umn.edu/tmuxgist <-- this document!

The Prefix Keystroke Ctrl-b

• Crtl-b c Create a new window
• Crtl-b <N> Switch to window <N>
• Crtl-b ? List available keystrokes
• Crtl-b , Rename current window

r17x

Once upon a time there was a user that wanted to install firefox.

The user tried to do pacman -S firefox but it didn't work. The all mighty pacman reported that firefox-3.2.4-1.i686.pkg.tar.gz could not be found on his mirror. So the user tried pacman -Sy firefox. It worked and the user rejoiced since he could once again go and troll /h/.

But all was not good. The user had made a grave error!

See, when the user told the almighty pacman to -Sy firefox, pacman did

r17x

open Belt;

[@bs.deriving abstract]
type queryConfig('data, 'key, 'fnParamsFilter) = {
  [@bs.optional]
  retry: int,
  [@bs.optional]
  retryDelay: int,
  [@bs.optional]
  initialData: unit => 'data,

r17x

Mutt + isync multiple accounts Unfinished

This is the setup that I use for mutt, I have two google domain account (read as gmail) and an institution where I work and study account. This means I have two gmail accounts and one outlook 365 account that i want to sync and read via mutt.

I want to store all my email locally as I travel a lot and will be in countries without easy internet access. For this I use mbsync (iSync). As it can handle multiple account types easily and efficently.

The setup works this way

[Remote Mail Servers] <= mbsync => [Local Mail Folders]

r17x

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

r17x

import { h, Component } from 'preact';
import Markup from 'preact-markup';
import register from './preact-custom-element';

// just a proxy component: WC -> Preact -> WC
const A = () => <x-b foo="initial foo from <x-a>" />;

// stateful component that can re-render
class B extends Component {
  render(props, state) {

r17x

I curate a list of interesting CLI tools, below are some command line tools that I personally love and use

• ripgrep - Search text for patterns fast.
• fzf - Command-line fuzzy finder.
• exa - Replacement for ls written in rust.
• git - Version control.
• youtube-dl - Download videos from YouTube and other video sites.
• tmux - Terminal multiplexer.
• direnv - Environment switcher for the shell.
• trash - Move files and folders to the trash.

r17x

10 JavaScript Terms You Should Know

From currying to closures there are quite a number of special words used in JavaScript. These will not only help you increase your vocabulary but also better understand JavaScript. Special terms are normally found in documentation and technical articles. But some of them like closures are pretty standard things to know about. Knowing what the word itself means can help you know the concept it's named for better.

1. Arity
2. Anonymous
3. Closure
4. Currying
5. Hoisting
6. Mutation