Stelios Sfakianakis sgsfak

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

layout	author	title	revision	version	description
default	mattmc3	Modern SQL Style Guide	2019-01-17	1.0.1	A guide to writing clean, clear, and consistent SQL.

Modern SQL Style Guide

Tailwind CSS best practices

Utility classes

When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!
Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.
Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

Mac Uninstall pkg Manually

using pkgutil

# list all your installed packages
pkgutil --pkgs

# show your package info
pkgutil --pkg-info

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?

Vim Tips

:g/^$/d      # Delete all blank lines

Spell

Fonte: Usando correção ortográfica no Vim7

Para habilitar a correção ortográfica no Vim7:

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-q, you need to add this to ~/.tmux.conf:

remap prefix to Control + q

	#!/bin/sh

	# Copyright (C) 2004 Joe Smith <[email protected]>
	# Copyright (C) 2004-2015 Wayne Davison <[email protected]>
	# Copyright (C) 2016-2018 YOSHIOKA Takuma <[email protected]>
	#
	# This program is free software: you can redistribute it and/or modify
	# it under the terms of the GNU General Public License as published by
	# the Free Software Foundation, either version 3 of the License, or
	# (at your option) any later version.

	# best practice: linux
	nano ~/.pgpass
	:5432::username:password
	chmod 0600 ~/.pgpass

	# best practice: windows
	edit %APPDATA%\postgresql\pgpass.conf
	:5432::username:password

	# linux

	#include <iostream>
	#include <stdio.h>
	#include <stdlib.h>
	#include <linux/ioctl.h>
	#include <linux/types.h>
	#include <linux/v4l2-common.h>
	#include <linux/v4l2-controls.h>
	#include <linux/videodev2.h>
	#include <fcntl.h>
	#include <unistd.h>