GORUCO 2017
as the organisers put it
GORUCO is a one day, single track, polyglot conference in New York City We’re rebuilding GORUCO as a polyglot conference that emphasizes and embodies the best of Ruby’s practices, values, and community. This is an opportunity to extend Ruby’s reach, to pull more people into Ruby’s orbit who share our values, and to keep Ruby alive even as its community members use a much broader set of tools and languages.
who it's for
Ruby developers, polyglot backend engineers, engineering managers, developer productivity engineers, technical leads, community organizers
topics
Rust ownership and borrowing; GraphQL on Rails; Elixir OTP GenServer patterns; polyglot persistence systems; developer productivity engineering frameworks; React on Rails server rendering; fast Ruby application startup; codes of conduct and mentorship; difficult conversations techniques; diversity-focused training pilots
| title | author | length |
|---|---|---|
| The Rubyist's Illustrated Rust Adventure Survival Guide | Liz Baillie | 23m |
A playable text-based adventure exists in both Ruby and Rust and the talk shows the actual code differences and the surprising result that the Rust version… | ||
| Optimizing for API Consumers with GraphQL | Brooks Swinnerton | 24m |
GitHub adopts GraphQL as a client-first API layer, implements it on Rails with the GraphQL Ruby gem, exposes a single /graphql endpoint and runs 100 million… | ||
| Trust and Teams | Rebecca Miller-Webster | 13m |
Defines trust as a risk assessment and maps it to concrete behaviors using BRAVING (boundaries, reliability, accountability, confidentiality, integrity… | ||
| Object Oriented Thinking with Elixir and OTP | Ryan Findley | 12m |
Claims that Erlang/Elixir processes behave like objects and shows it by building a contrived chat history service, implementing it first as a tail-recursive… | ||
| Developer Productivity Engineering | Panayiotis Thomakos | 11m |
Applies Google SRE principles to developer productivity with a concrete DPE framework that identify measure prioritize and a checklist of six toil criteria for… | ||
| SQL to NoSQL to NewSQL and the rise of polyglot persistence Paul Dix | Paul Dix | 31m |
Argues that SQL’s monopoly is over and polyglot persistence is the normal state, backing it with history (BigTable 2006, Dynamo 2007, Spanner 2012, Cockroach… | ||
| Difficult Conversations | Adam Cuppy | 36m |
Argues that difficult conversations improve when three concrete levers are changed: physiology language and focus. Gives a 60‑second breathing protocol —… | ||
| What I Learned to Love About Ruby When I Switched to Python | Lauren Ellsworth | 30m |
Compares concrete tradeoffs: Ruby’s principle of least surprise (methods with ? and !, synonyms like collect/map) versus Python’s strict whitespace errors… | ||
| Front-End Sadness to Happiness: The React on Rails Story | Justin Gordon | 36m |
Claims a practical integration: a react on Rails gem that wires Rails views to Webpack-built JS, registers components, and enables server rendering and… | ||
| Shaving my head made me a better programmer | Alex Qin | 10m |
Shaving appearance as an experiment produces an immediate change in how competence is perceived: shaved my head flips microaggressions into respect without any… | ||
| Beyond OSS | Veronica Lopez | 13m |
Many projects have weak codes of conduct, poor documentation, and assumptions that everyone uses Git or has the same time and workflows, which pushes newcomers… | ||
| Scars: On Handling Adversity | Ross Kaffenberger | 09m |
Claims that grief and career setbacks are recoverable are backed by concrete steps and examples: got counseling, rebuilt a career, and returned to work while… | ||
| How to Load 1m Lines of Ruby in 5s | Andrew Metcalf | 29m |
Claims reducing cold boot from 35s to 5s by statically analysing a multi‑million‑line Ruby monorepo and generating an autoloader build daemon. Process parses… | ||
| Type. Context. | Sam Phippen | 22m |
Shows concrete fixes rather than slogans: demonstrates adding forced error handling to a Faraday GET by requiring success and failure procs so callers must… | ||
| nothing matches | ||