csgo.ultimateL.3.A.list.core.markdown
ULTIMATE
Hello and welcome the the 3rd "ULTIMATE" list!
If you want to privatly contact me, either send me a PM on reddit, or add me on Steam/GabeNetwork, and PLEASE add a comment on my profile why you wanna add me first!
| #! /usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| """ | |
| "PYSTONE" Benchmark Program | |
| Version: Python/1.1 (corresponds to C/1.1 plus 2 Pystone fixes) | |
| Author: Reinhold P. Weicker, CACM Vol 27, No 10, 10/84 pg. 1013. |
| # Alternatively don't use slog but something else. I just like that more. | |
| [aliases] | |
| slog = log --pretty=format:"%C(auto,yellow)%h%C(auto)%d\\ %C(auto,reset)%s\\ \\ [%C(auto,blue)%cn%C(auto,reset),\\ %C(auto,cyan)%ar%C(auto,reset)]" | |
| addprx = "!f() { b=`git symbolic-ref -q --short HEAD` && \ | |
| git fetch origin pull/$1/head:pr/$1 && \ | |
| git fetch -f origin pull/$1/merge:PR_MERGE_HEAD && \ | |
| git rebase --onto $b PR_MERGE_HEAD^ pr/$1 && \ | |
| git branch -D PR_MERGE_HEAD && \ | |
| git checkout $b && echo && \ | |
| git diff --stat $b..pr/$1 && echo && \ |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
I've been wanting to do a serious project in Go. One thing holding me back has been a my working environment. As a huge PyCharm user, I was hoping the Go IDE plugin for IntelliJ IDEA would fit my needs. However, it never felt quite right. After a previous experiment a few years ago using Vim, I knew how powerful it could be if I put in the time to make it so. Luckily there are plugins for almost anything you need to do with Go or what you would expect form and IDE. While this is no where near comprehensive, it will get you writing code, building and testing with the power you would expect from Vim.
I'm assuming you're coming with a clean slate. For me this was OSX so I used MacVim. There is nothing in my config files that assumes this is the case.
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns on recent CPU
L2 cache reference ........................... 7 ns 14x L1 cache
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns 20x L2 cache, 200x L1 cache
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 4X memory
| #!/usr/bin/env bash | |
| # | |
| # This is sp, the command-line Spotify controller. It talks to a running | |
| # instance of the Spotify Linux client over dbus, providing an interface not | |
| # unlike mpc. | |
| # | |
| # Put differently, it allows you to control Spotify without leaving the comfort | |
| # of your command line, and without a custom client or Premium subscription. | |
| # |
I've kept quiet for awhile for various political reasons, but I now feel a kind of social responsibility to deter people from banking their business on MongoDB.
Our team did serious load on MongoDB on a large (10s of millions of users, high profile company) userbase, expecting, from early good experiences, that the long-term scalability benefits touted by 10gen