isaacsanders

This is a post by Joel Spolsky. The original post is linked at the bottom.

This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.

The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju

maxvt

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

beardicus

#
# fair-queue based settings for EdgeRouter Lite traffic shaping
#

# download is typically 30 and change. everything can burst to 100%
# of bandwidth, priority rules keep the garbage in check

set traffic-policy shaper download
set traffic-policy shaper download bandwidth 30Mbit

stympy

#!/usr/bin/env ruby

require 'helpscout'
require 'fileutils'

api_key = ARGV[0]
helpscout = HelpScout::Client.new(api_key)
helpscout.mailboxes.each do |box|
  FileUtils.mkdir(box.name) unless File.exists?(box.name)
  puts "Fetching #{helpscout.conversation_count(box.id, 'all', nil)} conversations for #{box.name}"

stevebowman

console.log('Loading event');

// Twilio Credentials 
var accountSid = '';
var authToken = '';
var fromNumber = '';

var https = require('https');
var queryString = require('querystring');

blackjid

Raspberry pi dashboard

This is what we did to setup a few dashboards at platanus

You'll need

• Raspberry Pi
• Dashing Service
• Wifi stick (optional)

s0enke

This is an adjusted version of EC2 CloudWatch stats for Dashing which is not bound to EC2 metrics but a generic widget for cloudwatch graphs. Visualization is done by Rickshawgraph as in the original example.

denji

• https://gitlab.com/qratorlabs/plag
• https://github.com/job/aggregate6
• https://github.com/flowchartsman/cidr-convert
• https://github.com/mhausenblas/cidrchk
• https://github.com/houqp/vpcstudio
• https://github.com/projectdiscovery/mapcidr
• https://github.com/FvDxxx/pfxaggr
• https://github.com/yl2chen/cidranger
• https://github.com/Kentik/patricia
• https://github.com/bgp/bgpq4

vjm

sudo apt-get install -y supervisor

sudo mkdir /usr/share/elasticsearch
cd /usr/share/elasticsearch

sudo wget https://download.elasticsearch.org/kibana/kibana/kibana-4.0.1-linux-x64.tar.gz
sudo wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.4.4.tar.gz
sudo wget https://download.elasticsearch.org/logstash/logstash/logstash-1.4.2.tar.gz

sudo tar -zxvf elasticsearch-0.90.0.tar.gz

DavidWittman

#!/usr/bin/env python

# Parses the output from AWS credential reports and displays
# users which have been inactive for 60+ days.
#
# Usage:
#   audit_iam_accounts.py credential_report.csv <days>
#

import csv