Skip to content

Instantly share code, notes, and snippets.

# Copied from http://ttaportal.org/wp-content/uploads/2012/10/7-Reallocation-using-LVM.pdf
##
## Showing the problem: need to reallocate 32GB from /dev/mapper/pve-data to /dev/mapper/pve-root
##
df -h
# Filesystem Size Used Avail Use% Mounted on
# /dev/mapper/pve-root 37G 37G 0 100% /
# tmpfs 2.0G 0 2.0G 0% /lib/init/rw
"""
gmaxwell's proof-of-storage
https://bitcointalk.org/index.php?topic=310323.0
"""
import random
from bisect import bisect_left
H = lambda v: (hash(("1",v)), hash(("2",v)))
def setup(k, seed):
@jvns
jvns / interview-questions.md
Last active January 14, 2026 10:57
A list of questions you could ask while interviewing

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

@brandongalbraith
brandongalbraith / interview-questions-cheat-sheet.md
Last active January 21, 2021 03:49 — forked from jvns/interview-questions.md
Interview Questions Cheat Sheet

Bitcoin provides Broadcast in a model where it's not clear otherwise how to get it.

Most distributed systems network models assume there is some kind of pre-established authenticated communication channel among a fixed set of participants, for example a PKI. Bitcoin is meant to work in a weaker model where there is no such assumption. Instead Bitcoin relies on a non-standard assumption about the allocation of computational resources - ignoring incentives for now, the assumption is that honest parties contribute more power in total than the adversary.

Some pre-established communication channel must still be assumed, just not an authenticated one. When formalizing Bitcoin things, I usually call it a "synchronous message diffusion" channel. Any honest party can publish a message, and that message is delivered to every other honest party within some time bound. A party that receives a message does not learn the identity of the sender (this essentially makes Sybil attacks possible). Additionally, the advers

@bitjockey42
bitjockey42 / mopidy.md
Created April 20, 2014 16:39
An installation and setup guide for mopidy on Arch Linux.

Mopidy on Arch Linux

mopidy

Installation

Install from the AUR.

@tsiege
tsiege / The Technical Interview Cheat Sheet.md
Last active May 13, 2026 14:18
This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.

ANNOUNCEMENT

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!






\

@debasishg
debasishg / gist:d9b6d984df3cc4681eb1
Last active November 23, 2022 06:26
Useful links on Convex Optimization
@kachayev
kachayev / concurrency-in-go.md
Last active September 23, 2025 16:12
Channels Are Not Enough or Why Pipelining Is Not That Easy
use list::Node;
mod list {
use std::mem;
#[derive(Show)]
pub struct Node<T> {
pub data: T,
prev: Option<Box<Node<T>>>,
next: Option<Box<Node<T>>>