Instance | Branch |
---|
/** | |
* Script to parse a Postman backupt to Insomnia keeping the same structure. | |
* | |
* It parses: | |
* - Folders | |
* - Requests | |
* - Environments | |
* | |
* Notes: Insomnia doesn't accept vars with dots, if you are using you must replace yours URLs manually (see ENVIRONMENTS_EXPORTS). | |
*/ |
function filterOutliers(someArray) { | |
if(someArray.length < 4) | |
return someArray; | |
let values, q1, q3, iqr, maxValue, minValue; | |
values = someArray.slice().sort( (a, b) => a - b);//copy array fast and sort | |
if((values.length / 4) % 1 === 0){//find quartiles |
# An example global gitignore file | |
# | |
# Place a copy if this at ~/.gitignore_global | |
# Run `git config --global core.excludesfile ~/.gitignore_global` | |
# Compiled source # | |
################### | |
*.com | |
*.class | |
*.dll |
From years of watching master programmers, I have observed certain common patterns in their workflows. From years of coaching skilled journeyman programmers, I have observed the absence of those patterns. I have seen what a difference introducing the patterns can make. Here are ways effective programmers get the most out of their precious 3e9 seconds on the planet. The theme here is scaling your brain. The journeyman learns to solve bigger problems by solving more problems at once. The master learns to solve even bigger problems than that by solving fewer problems at once. Part of the wisdom is subdividing so that integrating the separate solutions will be a smaller problem than just solving them together.
Slicing - Take a big project, cut it into thin slices, and rearrange the slices to suit your context. I can always slice projects finer and I can always find new permutations of the slices that meet different needs
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
I remember very clear I cry when I finish volume 3 of Knuth. | |
% | |
I am work on CSS SQL. | |
% | |
First sign of depression in devops is denial: you start of ignore Nagios alert. | |
% | |
In devops language is not success unless is another language++. | |
% | |
In devops you are addict to graph if first thought after orgasm is send duration and intensity to Graphite. | |
% |
#!/bin/bash | |
echo "Getting list of Availability Zones" | |
all_regions=$(aws ec2 describe-regions --output text --query 'Regions[*].[RegionName]' | sort) | |
all_az=() | |
while read -r region; do | |
az_per_region=$(aws ec2 describe-availability-zones --region $region --query 'AvailabilityZones[*].[ZoneName]' --output text | sort) | |
while read -r az; do |
(ns app.logging | |
(:refer-clojure :exclude [time]) | |
(:require #?(:clj [clojure.tools.logging :as log] | |
:cljs [goog.log :as glog])) | |
#?(:cljs (:import goog.debug.Console))) | |
#?(:cljs | |
(def logger | |
(glog/getLogger "app"))) |
#!/usr/bin/env /bin/sh | |
# SHA 256 based on openssl | |
# | |
# sha256 similar to the classic "md5sum" command line | |
# | |
if [ ${#} -gt 0 ] | |
then | |
# iterate over all arguments |