vedang

    - Specific Notmuch filters (and saved-searches) for:
      + The Feed (newsletters, blogs)
      + The Paper trail (receipts, ledger)
      + Screened Inbox (mail from folks you actually want to read)
      + Previously Seen (important mail that you've already read)
      + Unscreened Inbox (potential spam / stuff you don't want)
      
    - Elisp Functions to move / categorize emails from a particular sender. 
      + Adds tags needed by filters defined above to all email sent by a particular sender
      + Creates an entry in a DB file, which is used by the Notmuch post-new script when indexing new email, to auto-add the relevant tags.

fay59

Here's a list of mildly interesting things about the C language that I learned mostly by consuming Clang's ASTs. Although surprises are getting sparser, I might continue to update this document over time.

There are many more mildly interesting features of C++, but the language is literally known for being weird, whereas C is usually considered smaller and simpler, so this is (almost) only about C.

1. Combined type and variable/field declaration, inside a struct scope [https://godbolt.org/g/Rh94Go]

struct foo {
   struct bar {
 int x;

rand

Streaming Systems:

• Differential Dataflow - The code is ugly Rust, but the logic and linked papers are quite interesting.
• Spinning Fast Iterative Dataflows - Flink's execution model. Also, coverage in the Morning Paper.
• Discretized Streams - Spark Streaming's model of operation.
• Google's Dataflow Model - This is now also available as Apache (Incubating) Beam.
• Kafka Streams - Kafka offers "hipster stream processing," and a nice unification between tables and streams.

Streaming More G

rsampaio

Table of Contents

• 1. Week 1
  • 1.1. Introduction
    • 1.1.1. Logistics
    1.1.2. Material overview

jpillora

// A small SSH daemon providing bash sessions
//
// Server:
// cd my/new/dir/
// #generate server keypair
// ssh-keygen -t rsa
// go get -v .
// go run sshd.go
//
// Client:

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

jacobian

#!/bin/bash

read -p "Enter yubikey: " key
echo
curl "http://api.yubico.com/wsapi/2.0/verify?id=87&timeout=8&sl=50&nonce=askjdnkajsndjkasndkjsnad&timestamp=1&otp=$key"

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

darius

;; (mcase subject-expr (pattern action) ...)
(defmacro mcase (subject &rest clauses)
  `(funcall (mlambda ,@clauses) ,subject))

;; (mlambda (pattern action) ...)
(defmacro mlambda (&rest clauses)
  (if (null clauses)
      '(lambda (x) (match-error x))
      (let ((subject (gensym)) (fail (gensym)))
        `(lambda (,subject)

manuel

;; See http://okmij.org/ftp/continuations/implementations.html#dynamic-wind
;; and http://axisofeval.blogspot.com/2012/08/delimited-continuations-do-dynamic-wind.html

;; Slight trick here: use identity of yield-record-tag function as the actual tag
(define (yield-record-tag) yield-record-tag)
(define (make-yield-record v k)
  (list yield-record-tag v k))

;; Yield simply aborts up to the generator's caller, delivering to it
;; the yielded value and the continuation for resuming after the call