ArrrrCamp 2015
who it's for
Ruby developers, backend engineers, devops engineers, platform engineers, site reliability engineers, engineering managers, game developers
topics
runtime method tracing; keyword arguments internals; RSpec stubbing robustness; Docker for Rails apps; Docker Compose workflows; AMQP messaging with RabbitMQ; asynchronous message processing; chaos and resilience testing; database concurrency throttling; observability with system traces; design-for-developers practices; Gosu 2D game development
| title | author | length |
|---|---|---|
| Extremely Defensive Coding | Sam Phippen | 28m |
RSpec saves and restores real method implementations to make stubbing reliable across weird Ruby code and interpreters. It builds a robust method retrieval… | ||
| How to stay alive even when others go down:... | Florian Weingarten | 42m |
Shopify runs about 300k requests per minute and finds strict client timeouts cut cascading failures; circuit breakers stop repeated retries and are implemented… | ||
| Developing Ruby Applications with Docker | Laura Frank | 40m |
Claims Docker can supplant hypervisor VMs for Ruby apps and demonstrates concrete tooling and workflow: building images with a Dockerfile, pushing and finding… | ||
| Peeking into Ruby: Tracing Running Code | Jason R. Clark | 31m |
Shows concrete wins: run estrace to capture syscalls and find the exact failing open that returns “no such file or directory,” attach RB trace to a live… | ||
| Ruby keyword args and the options hash, from the parser to the virtual machine | Étienne Barri | 30m |
Argument handling turns out to be about implementation not syntax: Ruby treats keywords as an options hash under the hood, historical parser quirks cause… | ||
| Consequences of an Insightful Algorithm | Carina C. Zona | 32m |
Shows how deep learning and rule‑based code actually behave: a predictive algorithm detecting second trimester that exposed a teen, Shutterfly emails that… | ||
| Opening up to change | Andy Pike | 36m |
Promises to show how to make real code open for extension but closed for modification by refactoring a painful example through concrete steps, using Ruby and… | ||
| Developers, start designing! | Alexandra Leisse | 23m |
Concrete claim: when developers learn design and designers learn enough code, decisions happen faster and solutions actually fit constraints. Example: a… | ||
| Game Development - The Ruby way | Rishi Jain | 44m |
Ruby plus the Gosu 2D library actually runs on Mac Windows and Linux (MRI and Rubinius work, JRuby doesn’t), and development uses an initialize draw update… | ||
| Decouple all the things: Asynchronous messaging keeps it simple | Kerstin Puschke | 41m |
Demonstrates that AMQP messaging with RabbitMQ and the bunny gem in Ruby moves master‑data updates from fragile REST push to durable publish‑subscribe and task… | ||
| Day 1 Lightning Talks | 24m | |
A string of six minute reports that name concrete outcomes and tools not platitudes: a walking desk experiment that claims 13 million steps since 2012 and a… | ||
| Lightning Talks Day 2 | 40m | |
A rapid mix of concrete outcomes and tools: a free contributor sprint called Ross conf that reports 28 pull requests from 9 people and one attendee removing 13… | ||
| Stop Building Services, Episode 1: The Phantom Menace | Rachel Myers | 39m |
Argues that extracting services often increases fragility rather than reducing it, showing concrete failures: identity service creates two single points of… | ||
| nothing matches | ||