Paris Xavier Pinkney pxpgraphics

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

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

libdispatch efficiency tips

I suspect most developers are using the libdispatch inefficiently due to the way it was presented to us at the time it was introduced and for many years after that, and due to the confusing documentation and API. I realized this after reading the 'concurrency' discussion on the swift-evolution mailing-list, in particular the messages from Pierre Habouzit (who is the libdispatch maintainer at Apple) are quite enlightening (and you can also find some good tweets from him on the subject).

My take-aways are:

You should have very few queues that target the global pool. If all these queues are active at once, you will get as many threads running. These queues should be seen as execution contexts in the program (gui, storage, background work, ...) that benefit from executing in parallel. Start with few of them, reuse

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	// -------------------------------------
	// Swift Integer Quick Guide
	// -------------------------------------

	// Created by Keith Harrison http://useyourloaf.com
	// Copyright (c) 2017 Keith Harrison. All rights reserved.
	//
	// Redistribution and use in source and binary forms, with or without
	// modification, are permitted provided that the following conditions are met:
	//

	#########################
	# .gitignore file for Xcode4 and Xcode5 Source projects
	#
	# Apple bugs, waiting for Apple to fix/respond:
	#
	# 15564624 - what does the xccheckout file in Xcode5 do? Where's the documentation?
	#
	# Version 2.6
	# For latest version, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
	#

	[advice]
	# I know this stuff by now
	pushNonFastForward = false
	statusHints = false
	[alias]
	a = add
	ai = add --interactive
	ap = add --patch
	b = branch
	bl = blame

	[user]
	name = Pavan Kumar Sunkara
	email = [email protected]
	username = pksunkara
	[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
	[sendemail]
	smtpencryption = tls