Skip to content

Instantly share code, notes, and snippets.

View aisis's full-sized avatar

Aisis aisis

View GitHub Profile
@aisis
aisis / _verify-repair-permissions-disk.md
Created December 24, 2017 08:16 — forked from bzerangue/_verify-repair-permissions-disk.md
Mac OS X Utilities via Terminal: (Verify and Repair: Disk Permissions AND Disk / Software Update / TimeMachine)

Verify and Repair Disk Permissions via Terminal (Mac OS X)

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

Keybase proof

I hereby claim:

  • I am aisis on github.
  • I am aisis (https://keybase.io/aisis) on keybase.
  • I have a public key ASBlH5daFhSHEnj6xDGpXvoXZXJtxipdzQj00AAWK53Qggo

To claim this, I am signing this object:

Tiny Content Framework

About the project

This is a tiny content strategy framework focused on goals, messages, and branding. This is not a checklist. Use what you need and scrap the rest. Rewrite it or add to it. These topics should help you get to the bottom of things with clients and other people you work with.

Give me feedback on Twitter (@nicoleslaw) or by email (nicole@nicolefenton.com).

Contents

@aisis
aisis / Architecture.md
Created February 16, 2017 08:16 — forked from evancz/Architecture.md
Ideas and guidelines for architecting larger applications in Elm to be modular and extensible

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

  1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo
@aisis
aisis / gist:5ca26487ba5a9e862f8fd1b50c600d1f
Created November 11, 2016 18:16 — forked from cdevroe/gist:4fb3ebf7806b39020c33
Open Visual Studio Code from Terminal
code () {
if [[ $# = 0 ]]
then
open -a "Visual Studio Code" -n
else
[[ $1 = /* ]] && F="$1" || F="$PWD/${1#./}"
open -a "Visual Studio Code" -n --args "$F"
fi
}
@aisis
aisis / README.md
Created March 24, 2016 09:53
JavaScript Syntax Reference sheet.

JR Devleague Reference Sheet

If Else Statements

if(true){}