ZacSweers

Guidelines

To keep the arguments and examples to the point there are few helpful rules:

• No abstract examples/arguments. These cause the discussion to lose focus and make examples harder to follow. The example/argument must be traceable to a real-world problem - ___ is intended to solve real problems, not imaginary ones.
• Examples must show the full complexity of the problem domain. Simplified examples trivialize the problems and the solutions intended to solve those simplified examples may not work for the complex problems.
• Examples of problematic ___ code must be the “best way” of writing the code in ___ - if it can be improved then the improved version should be used instead.
• Arguments must be straight to the point and as concise as possible.
• Arguments should take the point of view of an average programmer - not the über-programmer who doesn’t make design mistakes.

smola

#!/bin/bash
set -e

if [[ -z ${K8S_JVM_POD} ]]; then
    echo "K8S_JVM_POD not defined"
    exit 1
fi

EXEC="kubectl exec ${K8S_JVM_POD}"
CP="kubectl cp ${K8S_JVM_POD}"

rylev

Rust in Large Organizations

Initially taken by Niko Matsakis and lightly edited by Ryan Levick

Agenda

• Introductions
• Cargo inside large build systems
• FFI
• Foundations and financial support