As easy as 1, 2, 3!
Updated:
- Aug, 08, 2022 update
config
docs for npm 8+ - Jul 27, 2021 add private scopes
- Jul 22, 2021 add dist tags
- Jun 20, 2021 update for
--access=public
- Sep 07, 2020 update docs for
npm version
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs
curl -o /dev/null -w "Connect: %{time_connect} TTFB: %{time_starttransfer} Total time: %{time_total} \n" http://inserturl.here |
#!/usr/bin/env python | |
# Simple script for finding and counting the color pages in a PDF | |
# Copyright (C) 2013-2019 Antonio Garcia-Dominguez | |
# Licensed under the GPLv3 | |
# | |
# This script is based on the following thread (thanks for the tip!): | |
# | |
# http://tex.stackexchange.com/questions/53493 | |
# |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.
Located in alphabetical order (not prefer)
C
ab
), also designed as a more modern replacement, written in C
golang
)class InstagramPrivateController < ApplicationController | |
def initialize(username, password, photo, caption) | |
@username = username | |
@password = password | |
@photo = photo | |
@caption = caption | |
@cookiepath = Tempfile.new('cookies').path | |
@user_agent = generate_user_agent() |
const React = require('react'); | |
const connectToStores = require('flummox/connect'); | |
function connect(...args) { | |
return function(target) { | |
return connectToStores(target, ...args); | |
} | |
} | |
http://thenewstack.io/monitoring-101-collecting-right-data/
Metrics capture a value pertaining to your systems at a specific point in time.
Metrics are usually collected once per second, one per minute, or at another regular interval to monitor a system over time.
For different Metric Data Types and the metric names they produce see https://docs.datadoghq.com/developers/metrics/types/?tab=histogram#metric-types
/.git/config
[remote "origin"]
url = ssh://[email protected]:7999/brikks/brikks.git
fetch = +refs/heads/*:refs/remotes/origin/*
fetch = +refs/pull-requests/*/from:refs/remotes/origin/pull-requests/*
fetch = +refs/pull-requests/*/merge:refs/remotes/origin/pull-requests-merge/*