rmtsrc

PostgreSQL JSON Cheatsheet

Using JSON in Postgres by example.

Quick setup via Docker

1. Download and install: Docker Toolbox
2. Open Docker Quickstart Terminal
3. Start a new postgres container:
   docker run --name my-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres

gnachman

set itermRunning to (application "iTerm" is running)
set scriptPath to quoted form of POSIX path of ((path to me as text) & "::" & "start.sh")
set user_shell to do shell script "dscl /Search -read /Users/$USER UserShell | awk '{print $2}'"

tell application "iTerm"
    activate
    if not (exists window 1) or (itermRunning = false) then
        reopen
    end if

mrlesmithjr

#!/bin/bash
#
# Larry Smith Jr.
# [email protected]
# @mrlesmithjr
# http://everythingshouldbevirtual.com
#
# Variables
DD_BS="512 1024 2048 4096 8192 16384 1048576"  #define blocksizes to test in Bytes [512=512b, 1024=1k, 2048=2k, 1048576=1MB]
DD_CONV_OPTIONS="fdatasync,notrunc"  #define the output options to pass to dd when creating TESTFILE

krider2010

# This would go into .bash_profile, .bashrc, .zshrc, etc.

# Script to start the gpg-agent - in it's own file as it is also used when the machine starts up
# Be sure to update the path to wherever you place this file!
# Note, depending on shell you may not need this line enabling, if the global daemon is already running
# OK. Some shells complain, others don't!
~/bin/startup-gpg-agent.sh

# GPG
if [ -f "${HOME}/.gpg-agent-info" ]; then

leonardofed

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules