We can look at two sides of the management coin: What do the individuals get out of it? And what benefit does the whole system derive from it?
I will disregard any benefits that accrue to managers just by holding the position of managing. Those are just circular logic. Circular logic abounds in discussions of management and hierarchy. For example, consider status reports. It will be said that status reports are necessary so managers know what their employees are working on. It’s
| (require '[clojure.core.async :refer [go alts! >! <! >!! <!! chan timeout]]) | |
| (defn buffered-chan | |
| "Reads from ch-source and if either timeout or the buffer-count has been | |
| read the result it sent to the channel thats returned from this function" | |
| ([ch-source buffer-count timeout-ms] | |
| (buffered-chan ch-source buffer-count timeout-ms 1)) | |
| ([ch-source buffer-count timeout-ms buffer-or-n] | |
| (let [ch-target (chan buffer-or-n)] | |
| (go |
| #!/bin/bash | |
| # | |
| # this script will attempt to detect any ephemeral drives on an EC2 node and create a RAID-0 stripe | |
| # mounted at /mnt. It should be run early on the first boot of the system. | |
| # | |
| # Beware, This script is NOT fully idempotent. | |
| # | |
| METADATA_URL_BASE="http://169.254.169.254/2012-01-12" |
Context: I was asked for a list of interesting reading relating to "distributed databases, behavior under partitions and failures, failure detection." Here's what I came up with in about an hour.
For textbooks, "Introduction to Reliable and Secure Distributed Programming" is a superb introduction to distributed computing from a formal perspective; it's really not about "programming" or "engineering" but about distributed system fundamentals like consensus, distributed registers, and broadcast. Used in Berkeley's Distributed Computing course (and HT to @lalithsuresh) Book Site
Notes from courses like Lorenzo Alvisi's Distributed Computing class can be great.
There are a bunch of classics on causality, [Paxos](ht
| #!/bin/sh | |
| ### | |
| # SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer) | |
| # For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos | |
| ### | |
| # Alot of these configs have been taken from the various places | |
| # on the web, most from here | |
| # https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx |
| This playbook has been removed as it is now very outdated. |
| #!/bin/sh | |
| # | |
| # init.d script for single or multiple unicorn installations. Expects at least one .conf | |
| # file in /etc/unicorn | |
| # | |
| # Modified by jay@gooby.org http://github.com/jaygooby | |
| # based on http://gist.github.com/308216 by http://github.com/mguterl | |
| # | |
| ## A sample /etc/unicorn/my_app.conf | |
| ## |
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
| # First verify the version of Java being used is not SunJSK. | |
| java -version | |
| # Get the latest Sun Java SDK from Oracle http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html | |
| wget http://download.oracle.com/otn-pub/java/jdk/7u1-b08/jdk-7u1-linux-i586.rpm | |
| # Rename the file downloaded, just to be nice | |
| mv jdk-7u1-linux-i586.rpm\?e\=1320265424\&h\=916f87354faed15fe652d9f76d64c844 jdk-7u1-linux-i586.rpm | |
| # Install Java |